Metrics collected using APMIA with remote jmx extension are missing some metrics compared to a previous installation using the jmx extension.
search cancel

Metrics collected using APMIA with remote jmx extension are missing some metrics compared to a previous installation using the jmx extension.

book

Article ID: 234178

calendar_today

Updated On:

Products

APM

Issue/Introduction

Using the APM Infrastructure Agent 21.6 with remote jmx extension there are some metrics that we are not seeing.

A previous installation with jmx extension allowed us to see those metrics.

Low Memory (should be under ResourceManager), OOME (should be under ResourceManager), Too Many Files Open (should be under ResourceManager), and ThreadCount (should be under java.lang type threading).  

I've attached comparison pictures.

We tried adding these statements to the instroscope.profile file and bundles.properties file to see if it would expose the above attributes but it didn't work.  Is there way to expose more metrics/attributes using the remote jmx extension like there was using the jmx extension?

introscope.agent.jmx.ratecounter.enable=true

introscope.agent.jmx.compositedata.enable=true

introscope.agent.jmx.excludeStringMetrics=false

introscope.agent.remotejmx.ratecounter.enable=true

introscope.agent.remotejmx.compositedata.enable=true

introscope.agent.remotejmx.excludeStringMetrics=false

Environment

Release : 20.2

Component : APM Agents

Resolution

New jmxclient.jar file provided to the customer.

This fix will be included in the next agent release.