[Kubernetes] Add both pod.{cpu,memory}.usage.node.pct and pod.{cpu,memory}.usage.limit.pct metrics to the Overview dashboard #10593
Conversation
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
…eats#39854 Signed-off-by: Tetiana Kravchenko <[email protected]>
Signed-off-by: Tetiana Kravchenko <[email protected]>
🚀 Benchmarks reportTo see the full report comment with |
|
Signed-off-by: Tetiana Kravchenko <[email protected]>
gizas
reviewed
Sep 9, 2024
packages/kubernetes/changelog.yml
Outdated
| # newer versions go on top | ||
| - version: 1.67.0 | ||
| changes: | ||
| - description: Adjust the Overview and Pods dashboards accordingly to https://github.com/elastic/beats/issues/39854 |
There was a problem hiding this comment.
Suggested change
| - description: Adjust the Overview and Pods dashboards accordingly to https://github.com/elastic/beats/issues/39854 | |
| - description: Adjust the Overview and Pods dashboards accordingly regarding pod.cpu.usage.node.pct. and pod.memory.usage.limit.pct |
There was a problem hiding this comment.
I would say to remove the pr as we dont use them in general.. wdyt?
gizas
approved these changes
Sep 9, 2024
…dashboard Signed-off-by: Tetiana Kravchenko <[email protected]>
Signed-off-by: Tetiana Kravchenko <[email protected]>
💚 Build Succeeded
History
|
|
gizas
approved these changes
Sep 9, 2024
MichaelKatsoulis
approved these changes
Sep 10, 2024
|
Package kubernetes - 1.67.0 containing this change is available at https://epr.elastic.co/search?package=kubernetes |
This was referenced Sep 25, 2024
4 tasks
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 4, 2025
…mory}.usage.limit.pct metrics to the Overview dashboard (elastic#10593) * adjust overview and pods dashboards corresponding to change elastic/beats#39854 Signed-off-by: Tetiana Kravchenko <[email protected]> * fix PR link Signed-off-by: Tetiana Kravchenko <[email protected]> * add cpu/mem per Pod Limit and per Node; fix the link to the overview dashboard Signed-off-by: Tetiana Kravchenko <[email protected]> * fix the pr description Signed-off-by: Tetiana Kravchenko <[email protected]> --------- Signed-off-by: Tetiana Kravchenko <[email protected]>
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 5, 2025
…mory}.usage.limit.pct metrics to the Overview dashboard (elastic#10593) * adjust overview and pods dashboards corresponding to change elastic/beats#39854 Signed-off-by: Tetiana Kravchenko <[email protected]> * fix PR link Signed-off-by: Tetiana Kravchenko <[email protected]> * add cpu/mem per Pod Limit and per Node; fix the link to the overview dashboard Signed-off-by: Tetiana Kravchenko <[email protected]> * fix the pr description Signed-off-by: Tetiana Kravchenko <[email protected]> --------- Signed-off-by: Tetiana Kravchenko <[email protected]>
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.
Proposed commit message
Overview dashboard: clarify that Top Cpu and Memory are Percentage of defined pod limit
Pods: filter pods that have
kubernetes.pod.cpu.usage.limit.pctandkubernetes.pod.memory.usage.limit.pct, it should be done explicitly on the top level, see related issue - [Lens] Ranking by the value is not working as expected kibana#189158Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Top CPU intensive podsandTop memory intensive podscharts #10522Screenshots
Before:
After:
