In the Agent, the yaml files for the following integrations are all read by JMXFetch:
This file can be found here: JMXFetch.py
There are two kinds of JMX attributes that JMXFetch is able to collect:
These are integer, float, double, long, boolean etc …
Note: Boolean values of true result in 1 and false in 0. Check the list of supported types
You can use the
list commands found here in order to get an idea of what your current JMX integration is collecting. Here is a snippet of that output showing a Simple attribute.
Matching: x/350. Bean name: domain:mybeanname - Attribute name: myattribute - Attribute type: java.lang.Integer
JMXFetch extracts the attribute value directly and use it as the metric value.
These can be seen as an array, a hashmap or an object composed of ‘simple attributes’.
Matching: x/350. Bean name: domain:mybeanname - Attribute name: myattribute - Attribute type: javax.management.openmbean.CompositeData In this case, we need to give more details to JMXFetch on how to use this ‘composite’ attribute to create a numerical value for a metric. In order to do this, you can use a . to specify the component, i.e.:
In the YAML configuration file is an example with java.lang HeapMemoryUsage composite attribute.
The best way to achieve this would be using JMXterm (see below). Note, for all versions of Agent v6, the
jmxterm JAR is not shipped with the Agent. To download and use
jmxterm, see the upstream project.
java -jar /opt/datadog-agent/agent/checks/libs/jmxterm-1.0-DATADOG-uber.jar -l localhost:PORT -u USER -p PASSWORD
Then use the get command to pull up a specific metric.