apollo_dashboard: use container_memory_rss for Pod Memory Limit Utilization panel#14201
Open
yonatanw-starkware wants to merge 2 commits into
Open
apollo_dashboard: use container_memory_rss for Pod Memory Limit Utilization panel#14201yonatanw-starkware wants to merge 2 commits into
yonatanw-starkware wants to merge 2 commits into
Conversation
|
This change is |
…zation panel Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
yonatanw-starkware
force-pushed
the
yonatanw/dashboard-memory-limit-panel-rss
branch
from
f0b5404 to
719cd57
Compare
… alerts Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
2 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.
Summary
container_memory_rssinstead ofcontainer_memory_working_set_bytesworking_setincludes active file-backed page cache which the kernel can reclaim, causing the panel to read near 100% even when there is no real OOM riskcontainer_memory_rss(anon memory only) correctly reflects actual memory pressure and OOM riskTest plan
dev_grafana.jsonregenerated correctly (2-line change in Pod Memory Limit Utilization panel expr)🤖 Generated with Claude Code