total_rss_bytes and total_pss_bytes from smaps_rollup

[blt]

What does this PR do?

This commit adds collection of total PSS bytes for all processes from
smaps_rollup, adjusting total_rss_bytes to also be from the same source

[blt]

• total_rss_bytes and total_pss_bytes from smaps_rollup #1134 👈 (View in Graphite)
• Slim out joinset #1133
• Expand smaps / smaps_rollup parsing #1130
• Move smaps and smaps_rollup parsing into modules #1129
• Rely on metrics registry to expire metrics #1128
• Remove target RSS_BYTE tracking #1127
• Migrate procfs memory module under procfs/ #1124
• Read all cgroup v2 metrics that can be read #1120
• Attempt generational storage of capture metrics #1125
• cargo-deny ding on an OSI license #1126
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[GeorgeHahn]

Change LGTM. Will this change the RSS measurement enough that we'll need to update limits to account for it?

[blt]

Change LGTM. Will this change the RSS measurement enough that we'll need to update limits to account for it?

My expectation is that these measurements will be basically the same, potentially slightly larger. smaps data elides < 1Kb because of the way it rounds, so if a target has a lot of little regions that'll matter.

Will need to be checked.

[scottopell]

We should deprecate rss_bytes (similar to total_rss_bytes but per-process) in favor of smaps_rollup.rss. OR define rss_bytes from smaps_rollup.rss

[blt]

Merge activity

• Dec 6, 3:33 PM EST: A user merged this pull request with Graphite.