Controlling JMX metrics in bundle.properties - how to configure the metric path

book

Article ID: 222367

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

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

The property we have changed is 

introscope.agent.remotejmx.system.s1.mbeanPatternsWhiteList=Catalina:type=Cache,*;Catalina:type=J2EEApplication,*;Catalina:type=ThreadPool,*;com.daon:type=DaonManagedEntity,*;metrics*:*

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

 

Cause

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

https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=4FyvRgeK85X7lYU0kAobbw==

Environment

Release : 10.7.0

Component :

Resolution

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"
configElements:
  - 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"

https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=+TXA0PFKF6j7Fpvho2sSBw==