Anon memory overage is not being alarmed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Eric MacDonald |
Bug Description
Brief Description
-----------------
The starlingX collectd memory monitoring plugin is no longer alarming Anon memory overage due to this previous commit.
https:/
The Anon (Anonymous) memory 'val.type' dispatched also needs to be changed from 'percent' to 'memory' like the platform memory was in that commit. See work around below.
Severity
--------
Minor: Anon memory overage is not alarmed
Steps to Reproduce
------------------
Consume more than 80% or Anon memory
Expected Behavior
------------------
Alarm should get raised after 3 minutes
Actual Behavior
----------------
No alarm is raised
Reproducibility
---------------
100% reproducible
System Configuration
-------
Any
Branch/Pull Time/Commit
-------
Any pull after Aug 24, 2021
Last Pass
---------
Prior to Aug 24, 2021
Timestamp/Logs
--------------
Logged but not alarmed
controller-0 collectd[95219]: info 4K memory usage: Anon: 95.2%, Anon: 56605.9 MiB, cgroup-rss: 56165.2 MiB, Avail: 2833.5 MiB, Total: 59439.5 MiB
controller-0 collectd[95219]: info 4K numa memory usage: node0, Anon: 92.16%, Anon: 56605.9 MiB, Avail: 4812.6 MiB, Total: 61418.6 MiB
Test Activity
-------------
Normal Use
Workaround
----------
Change the following lines from 'percent' to 'memory' on system and restart collectd
https:/
https:/
on system its
/opt/collectd/
Changed in starlingx: | |
assignee: | nobody → Eric MacDonald (rocksolidmtce) |
importance: | Undecided → Low |
tags: | added: stx.8.0 stx.monitor |
Fix proposed to branch: master /review. opendev. org/c/starlingx /monitoring/ +/868322
Review: https:/