APM - No system metrics

[RichardH (Richard Hepplestone)]

Hello,

I found a previous topic that said the system metrics in APM are not currently available

Elastic APM System Metrics fields data not being captured

Hi, I have configured Elasticsearch APM plugin & I am able to see most of the data except for system metric in which I am more interested. From the indices definition I can find list of system metrics fields as mentioned over here too: https://www.elastic.co/guide/en/apm/server/current/exported-fields-system.html But in discover tab I am not actually able to find any system metric level data, Currently I have configured " APM Node.js Agent" (https://www.elastic.co/guide/en/apm/agent/nodejs/c…

Is there any change to this? - I am just trying to confirm if me not getting metrics is a configuration issue or not.

Thanks

[axw (Andrew Wilkins)]

Hi Richard,

Welcome to the forum! All of the agents except for RUM capture a handful of common system metrics:

• system/process CPU usage
• system/process memory usage

Apart from those, recent versions of the agents collect additional runtime-specific metrics.

Which agent(s) are you using, and which version of the stack?

[RichardH (Richard Hepplestone)]

Hi Andrew,

Thanks for the reply.

I am using version 7.1.1 monitoring a Tomcat Java app server. To set it up I copied the elastic-apm-agent-1.7.0.jar file to the app server and edited the wrapper.conf in Tomcat with the following:

wrapper.java.additional.9=-Delastic.apm.service_name=tomcat,swee-cis,swee-lpa,swee-lps,swee-mobs-server,swee-mwb,swee-portal,swee-sdc

wrapper.java.additional.10=-Delastic.apm.application_packages=*

wrapper.java.additional.11=-Delastic.apm.server_urls=http://hostname:8200

wrapper.java.additional.12=-javaagent:/<agent_dir>/elastic-apm-agent-1.7.0.jar

update - I have upgraded to 7.2. The Metric dashboard now looks different as it includes charts for Heap memory, but still no data. If I look at the events coming through there is nothing that identifies the system name. My guess is I have missed something on the config.

[Eyal_Koren]

Hi Richard,

@RichardH

wrapper.java.additional.9=-Delastic.apm.service_name=tomcat,swee-cis,swee-lpa,swee-lps,swee-mobs-server,swee-mwb,swee-portal,swee-sdc

This config option doesn't support a list, only a single value. You can either omit this config (in order to get a service per web application in your tomcat) or use with a single value for a service name to be used for the entire tomcat. Please read the documentation. If you omit the service_name in order to rely on automatic service name discovery - be aware of the caveat documented regarding metrics. Otherwise- use a single value.

@RichardH

wrapper.java.additional.10=-Delastic.apm.application_packages=*

Not a valid config for this. Instead, use the root package for your app code (eg co.elastic) or a comma-separated list of packages (eg co.elastic,org.elasticsearch).

I hope this helps,
Eyal.