[Metricbeat] Add memory PSI metrics for cgroupv2#48054
[Metricbeat] Add memory PSI metrics for cgroupv2#48054orestisfl merged 13 commits intoelastic:mainfrom
Conversation
Add memory pressure PSI metrics to the system.process.cgroup.memory
metricset, complementing the existing CPU and IO pressure metrics.
New fields added under system.process.cgroup.memory.pressure:
- pressure.some.{10,60,300}.pct - Share of time with some tasks stalled
- pressure.some.total - Total some pressure time
- pressure.full.{10,60,300}.pct - Share of time with all tasks stalled
- pressure.full.total - Total full pressure time
Closes elastic#47604
🤖 GitHub commentsJust comment with:
|
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
🔍 Preview links for changed docs |
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
colleenmcginnis
left a comment
There was a problem hiding this comment.
Starting with v9.0, there is no longer a new documentation set published with every minor release: the same page stays valid over time and shows version-related evolutions (ref). As a result, we add version information in the fields.yml and it adds version badges to the generated Markdown file. Read more in Contributing to the docs.
Based on the backport labels, I assumed these changes are targeting 9.3.0, but feel free to adjust as needed. After applying the suggestions you'll have to regenerate the docs.
Co-authored-by: Colleen McGinnis <colleen.j.mcginnis@gmail.com>
|
You'll have to regenerate the docs ( |
Proposed commit message
Add memory pressure PSI metrics to the system.process.cgroup.memory
metricset, complementing the existing CPU and IO pressure metrics.
New fields added under system.process.cgroup.memory.pressure:
Closes #47604
Checklist
I have made corresponding change to the default configuration filesstresstest.shscript to run them under stress conditions and race detector to verify their stability../changelog/fragmentsusing the changelog tool.How to test this PR locally
1. Build and Run Metricbeat
2. Create Test Configuration
3. Run Metricbeat
4. Verify Memory Pressure Fields
Look for
system.process.cgroup.memory.pressurein the output:5. Compare Before/After (Optional)
compare-psi-metrics.sh
Use the comparison script to compare output from main vs this PR:
Related issues