ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Controlling JMX metrics in - how to configure the metric path


Article ID: 222367


Updated On:


CA Application Performance Management (APM / Wily / Introscope)


We have tried controlling JMX metrics from of Jmx extension in Java agent.

The property we have changed is 


by adding com.daon values to see under JMX but unable to see them even after agent restart.



The metrics were reporting but they are appearing under the Default branch and they were looking to get them at the top level


Release : 10.7.0

Component :


Using the modules feature of the JMX extension metric paths can be specified however there is no mechanism in the module definition to shift the entire branch so each attribute would need to be specific individually e.g. The location prior to the module configuration shown in Red and the modified location shown in Green


version: "1.0"
  - objectName: "Catalina:*"
    attribute: "acceptCount"
    metricName: "{rootNode}|{domain}|name={name}|Type={type}:{attribute}"
    metricType: "counter"
  - objectName: "Catalina:*"
    attribute: "foo"
    metricName: "{rootNode}|{domain}|name={name}|Type={type}:{attribute}"
    metricType: "counter"