Cherry-pick #19675 to 7.x: Fix nanocore sum for non default intervals on Kubernetes Overview Dashboard #19978
Conversation
This file contains 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
…hboard (elastic#19675) * Fix nanocore sum for non default intervals on Kubernetes Overview Dashboard The Kibana visualization CPU usage by node [Metricbeat Kubernetes] ECS did not account for x-axis scaling. In case the scaling aligned with the value from metricset.period it was correct. In every other case, the sum was not correctly calculated as it did not take into account how big the buckets in the visualizations would be. * Add changelog entry for k8s dashboard node usage (cherry picked from commit 4dcbde3)
ChrsMark
added
[zube]: In Review
backport
Team:Platforms
botelastic
bot
added
the
needs_team
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
botelastic
bot
removed
the
needs_team
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cherry-pick of PR #19675 to 7.x branch. Original message:
Bug
What does this PR do?
The Kibana visualization
CPU usage by node [Metricbeat Kubernetes] ECSdid not account for x-axis scaling.In case the scaling aligned with the value from metricset.period it was correct.
In every other case, the sum was not correctly calculated as it did not take into account how big the buckets in the visualizations would be.
Why is it important?
It allows to correctly see the usage of nodes on the Kubernetes Dashboard on longer time ranges.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Screenshots
Confirmed working on non 10 seconds scaling.
