Hi all,
I try to do some JMX based monitoring with AppDynamics. I have an MBean, which exposes an attribute of type HashMap<String, Long>. I want to have a separate metric for each entry, the Long value should be the metric value.
I tried several approaches, also using MBean Getter Chain (like get("key")), which should enable me to access the values, but the metric simply does not show up in the metric browser, while other metrics I defined, based on plain Long attributes, work fine.
Has anyone here deeper experience in defining JMX Match Rules, especially with complex objects exposed as attributes?
Cheers!
Stefan
Hi Stefan,
Apologies for delay in response, Provide below details if this is still an issue, to better debug this:
- screenshot of JMX rule in edit view from Configure -> instrumentation -> Transaction detection in UI
- screenshot of target JMX mbean object mbean attribute in view from node dashboard -> jmx -> mbean browser screen
- attach agent logs folder archive