Repository navigation
[Monitoring] Do not use the normalized derivative value - #27416
Merged
Merged
Conversation
Contributor
💔 Build Failed |
Contributor
💚 Build Succeeded |
Contributor
|
Pinging @elastic/stack-monitoring |
Contributor
Author
|
cc @pickypg |
ycombinator
approved these changes
Dec 20, 2018
ycombinator
left a comment
Contributor
There was a problem hiding this comment.
Functionally LGTM. Elegant fix!
2 of 3 tasks
patrykkopycinski
pushed a commit
to patrykkopycinski/kibana
that referenced
this pull request
May 6, 2026
* Use the non normalized value * Update keys used in tests
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Relates to elastic/beats#9377
This PR updates the math used to calculate CPU utilization to not use the normalized derivative value, but instead use the default value. In this situation, it seems the normalized derivative (read docs here) is not what the user expects to see as the % values will not match what their system is reporting.
See the beats issue for reproduction steps.