We are running AppInternals agent on a Red Hat Enterprise Linux 7.x and the percentage Memory Usage metric is being reported incorrectly in the webUI when we compare it to what the system is actually using.
What is causing this issue and how to fix it?
Incorrect percentage Memory Usage being reported in AppInternals Analysis server Memory Card for RHEL 7.x agents
Description
Solution
The OS Sub-agent running on Linux systems currently calculates the percentage Memory Usage metric using the formula as below
The above metrics are picked by the sub-agent from
However on newer systems like RHEL 7.x we can find a new metric called MemAvailable which should be used in calculating the %Memory Usage. This is currently not being done in the code which might result in incorrect Memory Usage values when compared to value which you might obtain from the server itself (
This is a known issue and is being worked on by R&D, to make use of the new metric when available.
For more detail on MemAvailable metric please take a look at the below link
https://unix.stackexchange.com/questions/261247/how-can-i-get-the-amount-of-available-memory-portably-across-distributions
%Mem Usage = MemTotal - MemFree
------------------------------- * 100
MemTotal The above metrics are picked by the sub-agent from
/proc/meminfo However on newer systems like RHEL 7.x we can find a new metric called MemAvailable which should be used in calculating the %Memory Usage. This is currently not being done in the code which might result in incorrect Memory Usage values when compared to value which you might obtain from the server itself (
free -h). This is a known issue and is being worked on by R&D, to make use of the new metric when available.
For more detail on MemAvailable metric please take a look at the below link
https://unix.stackexchange.com/questions/261247/how-can-i-get-the-amount-of-available-memory-portably-across-distributions
Environment
AppInternals agent, RHEL kernel 3.14 and later
Related Bugs
Attachments
Related Files
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case