topic Re: How does JMX2.0 extension matches the jmx metric name to internal metric name in Extensions

How does JMX2.0 extension matches the JMX metric name to internal metric name

Abhay_SAP — Mon, 19 Aug 2024 07:57:42 GMT

Hi,

I have a CF application which publishes a metric named "gb.request.count" to JMX. My extension.yaml file used in JMX2.0 defines the metric as follows:

metrics:
- key: cpi.it-gb.gb.request
metadata:
displayName: IT-GB Total Request Count
description: IT-GB Total Request Count
unit: Count
sourceEntityType: process_group_instance
tags:
- JMX

The dynatrace shows the metric properly.

My question is how is "cpi.it-gb.gb.request" mapped to "gb.request.count"?

Thanks,

Abhay

Re: How does JMX2.0 extension matches the jmx metric name to internal metric name

Mike_L — Tue, 02 Jul 2024 11:21:55 GMT

The snippet you shared is from the metric metadata. This section of the yaml is only responsible for display names and units and such, no matter the source.

Inside your YAML you also have the the JMX section where you give the metric an ID based on the mbean attribute. If you want to rename the ID of the metric and remove "cpi.it-" from the metric ID, that's the easiest place to do that.

If you're just wondering why it added "count" at the end of the metric, that's because you defined this as a count metric in the jmx section of the YAML.

Re: How does JMX2.0 extension matches the jmx metric name to internal metric name

Abhay_SAP — Tue, 02 Jul 2024 11:37:55 GMT

Hi Mike,

Thank you for the response. I have attached a text file which contains the jmx section too.

My application is pushing the metric to JMX with bean name as "gb.request.count" and the extension file does not have this name anywhere. extension has "cpi.it-gb.gb.request". I am failing to understand how does dynatrace maps cpi.it-gb.gb.request to gb.request.count and display the metric.

Thanks,

Abhay

Re: How does JMX2.0 extension matches the jmx metric name to internal metric name

Mike_L — Thu, 04 Jul 2024 15:54:38 GMT

Inside your yaml you have this section. We fetch the Count attribute from the JMX query you have defined under "query":

jmx: groups: - group: jmx subgroups: - subgroup: metrics:name=gbRequestCount.systemId.dummyId,* query: metrics:name=gbRequestCount.systemId.dummyId,* metrics: - key: cpi.it-gb.gb.request value: attribute:Count type: gauge - key: cpi.it-gb.gb.request.count.rate.count value: attribute:Count type: count