API Gateway EPAgent Reporting Wrong values for Memory Usage and CPU
search cancel

API Gateway EPAgent Reporting Wrong values for Memory Usage and CPU


Article ID: 138745


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE


CA Application Performance Management (APM) product displays free memory for our Linux systems in Kilobytes, but when we use the Linux free command we see the free memory is actually much larger (Megabytes  instead of Kilobytes).

We also find that EPAgent is displaying CPU utilization much higher than actual utilization. When we look at CPU utilization with the Linux top command or through our vSphere Client it is less than what APM is displaying through the Investigator. 

We assume this is a problem with the EPAgent that is running on the Gateway for sending metrics to APM.


Release : 10.7.0

Component : APM Agents


If you review the IntroscopeEPAgent.properties file under epagent directory, you will see the following entries.


introscope.epagent.stateless.OS_RESOURCE.command=perl /opt/apm105/epagent/epaplugins/apim/gatewayOSResource.pl


introscope.epagent.stateless.OPERATING_STATUS.command=perl /opt/apm105/epagent/epaplugins/apim/gatewayOperatingStatus.pl


The default EPAgent does not have these entries. These are added by CA API Gateway team. The resource metrics are coming from script /opt/apm105/epagent/epaplugins/apim/gatewayOSResource.pl

This script is installed by CA API Gateway.

This CA API Gateway script is sending the wrong values to EPAgent which we see in the APM UI.

Consult with  CA API Gateway support team how to proceed further