The JMX collector uses Jolokia to collect data on your MBeans. Jolokia is an agent that provides access to JMX MBeans without having to write any Java code. Metricly can be used to process and graph the data collected by Jolokia. This can be useful if you’d like to collect a small set of metrics via JMX e.g., garbage collection metrics on your Cassandra cluster.
Java Integration Options
We have several different options for monitoring Java applications. Each method varies in terms of setup difficulty and the amount / type of information it collects. See the table below for more information.
|Ananke||Java library you can use to push metrics to the StatsD listener embedded in our Linux agent.
his approach requires that you integrate the StatsDReporter into your applications.
|Dropwizard||Integrate the dropwizard-metrics library into your Dropwizard application and configure it to send metrics to the StatsD listener embedded in ourLinux agent.|
|Iris||Java library you can use to push metrics directly to Metricly’s REST API.|
|Java Agent||Open-source and open-license Java agent the does the byte-code instrumentation for you. No changes to source code required.|
|JMX||Integration that relies on our Linux agent to collect JVM metrics (e.g., heap size, garbage collection, etc.) without code-level instrumentation.|
- Download the Jolokia JVM JAR file.
- Move the downloaded file to the /opt/netuitive-agent/ directory.
- Pass the Java agent parameter into your application.
- Navigate to the collectors folder.
The default location is /opt/netuitive-agent/conf/collectors.
- Open the JolokiaCollector.conf file.
This configuration file will only be available in agent versions 0.3.1 or later. Otherwise, you will have to create a configuration file with the same name.
- Change the
enabledsetting to True.
- Save the configuration file, and restart the Linux Agent.