Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scale system.cpu.*.pct metrics by the number of cores #4544

Merged
merged 1 commit into from
Jun 23, 2017

Conversation

andrewkroh
Copy link
Member

@andrewkroh andrewkroh commented Jun 22, 2017

Change all system.cpu.*.pct metrics to be scaled by the number of CPU cores such that the values range on [0, 100% * number_of_cores]. This will make the CPU usage percentages from the system cpu metricset consistent with the system process metricset. The documentation for these metrics already stated that on multi-core systems the percentages could be greater than 100%. This makes the code match the docs, but does cause a change in behavior to the user.

Change all `system.cpu.*.pct` metrics to be scaled by the number of CPU cores such that the values range on `[0, 100% * number_of_cores]`. This will make the CPU usage percentages from the system cpu metricset consistent with the system process metricset. The documentation for these metrics already stated that on multi-core systems the percentages could be greater than 100%. This makes the code match the docs, but does cause a change in behavior to the user.
@andrewkroh andrewkroh force-pushed the bugfix/5_5-system-cpu-pct-scaled branch from b28d2f2 to cf45bc6 Compare June 22, 2017 20:54
@@ -6,14 +6,14 @@
- name: cores
type: long
description: >
The number of CPU cores.
The number of CPU cores. The CPU percentages can range from `[0, 100% * cores]`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you intend to add this here? Is it to explain how is the number of cores useful?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it was intentional (for the reason you mentioned above).

Copy link
Contributor

@tsg tsg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@tsg
Copy link
Contributor

tsg commented Jun 23, 2017

Taking it in, to make sure it makes the cut for 5.5.0.

@tsg tsg merged commit 67e2064 into elastic:5.5 Jun 23, 2017
andrewkroh added a commit to andrewkroh/beats that referenced this pull request Jun 23, 2017
Change all `system.cpu.*.pct` metrics to be scaled by the number of CPU cores such that the values range on `[0, 100% * number_of_cores]`. This will make the CPU usage percentages from the system cpu metricset consistent with the system process metricset. The documentation for these metrics already stated that on multi-core systems the percentages could be greater than 100%. This makes the code match the docs, but does cause a change in behavior to the user.
(cherry picked from commit 67e2064)
tsg pushed a commit that referenced this pull request Jun 26, 2017
Change all `system.cpu.*.pct` metrics to be scaled by the number of CPU cores such that the values range on `[0, 100% * number_of_cores]`. This will make the CPU usage percentages from the system cpu metricset consistent with the system process metricset. The documentation for these metrics already stated that on multi-core systems the percentages could be greater than 100%. This makes the code match the docs, but does cause a change in behavior to the user.
(cherry picked from commit 67e2064)
@andrewkroh andrewkroh deleted the bugfix/5_5-system-cpu-pct-scaled branch July 5, 2017 19:23
@tsg tsg mentioned this pull request Jul 24, 2017
28 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants