Stackdriver Monitoring can monitor Java Virtual Machine processes for common Java metrics.
JVM metrics are collected when you configure one or more of the following Java-based plugins with Stackdriver Monitoring:
JVM metrics are displayed on the JVM Services page in the Resources menu. After you install the monitoring agent and configure one of the Java-based plugins, Stackdriver Monitoring populates the JVM Services page with inventory and metrics.
Configuring Stackdriver Monitoring to monitor Java VMs
After you install the monitoring agent,
use the following instructions to configure the JVM plugin on your instances.
For instructions on upgrading from the legacy
jmxtrans monitoring, see
Upgrading from jmxtrans below.
The JVM plugin requires version 5.5.0-257 or later of the monitoring agent. To update the agent, see Upgrading the agent.
Enabling the JVM monitoring plugin
Java Virtual Machines are monitored via JMX.
(cd /opt/stackdriver/collectd/etc/collectd.d/ && curl -O https://raw.githubusercontent.com/Stackdriver/stackdriver-agent-service-configs/master/etc/collectd.d/jvm-sun-hotspot.conf)
Edit the downloaded configuration file and replace
JMX_PORT by the port on which your JVM is
to allow JMX connections.
After adding the configuration file, restart the monitoring agent by running the following command:
sudo service stackdriver-agent restart
Information on other plugin configuration options can be found at collectd.org.
What is monitored
The JVM plugin monitors the following common JVM metrics:
- Active JVM Threads
- JVM Heap memory usage
- JVM Non-Heap memory usage
- JVM Open File Descriptors
- JVM Garbage Collection Count
Upgrading from jmxtrans
If you are currently running a VM with the legacy
you need to upgrade all of the Java-based plugins, namely
Tomcat. After you've upgraded those plugins
and restarted the
stackdriver-agent service, you can shut down the
process. You can then uninstall
jmxtrans by removing the
tree and the
/etc/init.d/jmxtrans script (if the script is present).