updated HCP container memory usage metric

[mukrishn]

Type of change

• [x] Refactor
• [ ] New feature
• [ ] Bug fix
• [ ] Optimization
• [ ] Documentation Update

Description

Changed query for monitoring HCP pod usage, capture container memory usage from container_memory_working_set_bytes instead of container_memory_rss. OOM killer is watching the former to kill the process if it exceeds(only if resource limit is set), so it would be better to report working set metrics to know its actual usage, it does not include cache or swap.

This blog helps to understand it better other container metrics too.

Related Tickets & Documents

• Related Issue #
• Closes #

Checklist before requesting a review

• [ ] I have performed a self-review of my code.
• [ ] If it is a core feature, I have added thorough tests.

Testing

• Please describe the System Under Test.
• Please provide detailed steps to perform tests related to this code change.
• How were the fix/results from this change verified? Please provide relevant screenshots or results.