JVM Stay organized with collections Save and categorize content based on your preferences.
The JVM integration collects JVM metrics exposed throughJava ManagementExtensions (JMX).The integration primarily collects metrics on memory and garbage collection.Additional runtime metrics, such as thread count and classes loaded, are alsoavailable.
For more information about JVM, see theJVM documentation.
Prerequisites
To collect JVM telemetry, you mustinstall the Ops Agent:
- For metrics, install version 2.2.0 or higher.
PATH variablethat includes the JVM executable must be available to thegoogle-cloud-ops-agent-opentelemetry-collector service.If you didn't install the JDK by using a package manager,or if you installed it into a non-standard location, then you can modify thesystemd environment to include the path by using thesystemctl set-environment command.This integration supports JVM versions Java 16 and Java 11.
Configure your JVM instance
To expose a JMX endpoint, you must set thecom.sun.management.jmxremote.portsystem property when starting the JVM. We also recommend setting thecom.sun.management.jmxremote.rmi.port system property to the same port.
To expose a JMX endpoint remotely, you must also set thejava.rmi.server.hostname system property.
To set system properties by using command-line arguments, prepend the propertyname with-D when starting the JVM.
For example, to setcom.sun.management.jmxremote.port to port9999, specifythe following when starting the JVM:
-Dcom.sun.management.jmxremote.port=9999
Configure the Ops Agent for JVM
Following the guide toConfigure the OpsAgent, add the required elementsto collect telemetry from JVM instances, andrestart the agent.
Example configuration
The following commands create the configuration to collect and ingest telemetryfor JVM:
set-e#Checkifthefileexistsif[!-f/etc/google-cloud-ops-agent/config.yaml];then#Createthefileifitdoesn'texist.sudomkdir-p/etc/google-cloud-ops-agentsudotouch/etc/google-cloud-ops-agent/config.yamlfi#Createabackupoftheexistingfilesoexistingconfigurationsarenotlost.sudocp/etc/google-cloud-ops-agent/config.yaml/etc/google-cloud-ops-agent/config.yaml.bak#ConfiguretheOpsAgent.sudotee/etc/google-cloud-ops-agent/config.yaml >/dev/null <<EOFmetrics:receivers:jvm:type:jvmendpoint:service:jmx:rmi:///jndi/rmi://127.0.0.1:9010/jmxrmiservice:pipelines:jvm:receivers:-jvmEOFFor these changes to take effect, you must restart the Ops Agent:
Linux
- To restart the agent, run the following command on your instance:
sudo systemctl restart google-cloud-ops-agent
- To confirm that the agent restarted, run the following command and verify that the components "Metrics Agent" and "Logging Agent" started:
sudo systemctl status "google-cloud-ops-agent*"
Windows
- Connect to your instance using RDP or a similar tool and login to Windows.
- Open a PowerShell terminal with administrator privileges by right-clicking the PowerShell icon and selectingRun as Administrator
- To restart the agent, run the following PowerShell command:
Restart-Service google-cloud-ops-agent -Force
- To confirm that the agent restarted, run the following command and verify that the components "Metrics Agent" and "Logging Agent" started:
Get-Service google-cloud-ops-agent*
Configure metrics collection
To ingest metrics from JVM, you must create a receiver for the metricsthat JVM produces and then create a pipeline for the new receiver.
This receiver does notsupport the use of multiple instances in the configuration, for example, tomonitor multiple endpoints. All such instances write to the same time series,and Cloud Monitoring has no way to distinguish among them.
To configure a receiver for yourjvm metrics, specify the followingfields:
| Field | Default | Description |
|---|---|---|
collection_interval | 60s | Atime duration value, such as30s or5m. |
endpoint | localhost:9999 | TheJMX Service URL or host and port used to construct the service URL. This value must be in the form ofservice:jmx:<protocol>:<sap> orhost:port. Values inhost:port form are used to create a service URL ofservice:jmx:rmi:///jndi/rmi://<host>:<port>/jmxrmi. |
password | The configured password if JMX is configured to require authentication. | |
type | This value must bejvm. | |
username | The configured username if JMX is configured to require authentication. |
What is monitored
The following table provides the list of metrics that the Ops Agent collectsfrom the JVM instance.
| Metric type | |
|---|---|
| Kind, Type Monitored resources | Labels |
workload.googleapis.com/jvm.classes.loaded | |
GAUGE, INT64gce_instance | |
workload.googleapis.com/jvm.gc.collections.count | |
CUMULATIVE, INT64gce_instance | name |
workload.googleapis.com/jvm.gc.collections.elapsed | |
CUMULATIVE, INT64gce_instance | name |
workload.googleapis.com/jvm.memory.heap.committed | |
GAUGE, INT64gce_instance | |
workload.googleapis.com/jvm.memory.heap.init | |
GAUGE, INT64gce_instance | |
workload.googleapis.com/jvm.memory.heap.max | |
GAUGE, INT64gce_instance | |
workload.googleapis.com/jvm.memory.heap.used | |
GAUGE, INT64gce_instance | |
workload.googleapis.com/jvm.memory.nonheap.committed | |
GAUGE, INT64gce_instance | |
workload.googleapis.com/jvm.memory.nonheap.init | |
GAUGE, INT64gce_instance | |
workload.googleapis.com/jvm.memory.nonheap.max | |
GAUGE, INT64gce_instance | |
workload.googleapis.com/jvm.memory.nonheap.used | |
GAUGE, INT64gce_instance | |
workload.googleapis.com/jvm.memory.pool.committed | |
GAUGE, INT64gce_instance | name |
workload.googleapis.com/jvm.memory.pool.init | |
GAUGE, INT64gce_instance | name |
workload.googleapis.com/jvm.memory.pool.max | |
GAUGE, INT64gce_instance | name |
workload.googleapis.com/jvm.memory.pool.used | |
GAUGE, INT64gce_instance | name |
workload.googleapis.com/jvm.threads.count | |
GAUGE, INT64gce_instance | |
Verify the configuration
This section describes how to verify that you correctly configured theJVM receiver. It might take one or twominutes for the Ops Agent to begin collecting telemetry.
To verify that JVM metrics are being sent toCloud Monitoring, do the following:
In the Google Cloud console, go to theleaderboard Metrics explorer page:
If you use the search bar to find this page, then select the result whose subheading isMonitoring.
- In the toolbar of thequery-builder pane, select the button whose name is eithercode MQL orcode PromQL.
- Verify thatPromQL is selectedin theLanguage toggle. The language toggle is in the same toolbar thatlets you format your query.
- Enter the following query in the editor, and then clickRun query:
{"workload.googleapis.com/jvm.memory.heap.used", monitored_resource="gce_instance"}
View dashboard
To view your JVM metrics, you must have a chart or dashboardconfigured.The JVM integration includes one or more dashboards for you.Any dashboards are automatically installed after you configure theintegration and the Ops Agent has begun collecting metric data.
You can also view static previews of dashboards withoutinstalling the integration.
To view an installed dashboard, do the following:
In the Google Cloud console, go to the
Dashboards page:If you use the search bar to find this page, then select the result whose subheading isMonitoring.
- Select theDashboard List tab, and then choose theIntegrations category.
- Click the name of the dashboard you want to view.
If you have configured an integration but the dashboard has not beeninstalled, then check that the Ops Agent is running. When there is nometric data for a chart in the dashboard, installation of the dashboard fails.After the Ops Agent begins collecting metrics, the dashboard is installedfor you.
To view a static preview of the dashboard, do the following:
In the Google Cloud console, go to the
Integrations page:If you use the search bar to find this page, then select the result whose subheading isMonitoring.
- Click theCompute Engine deployment-platform filter.
- Locate the entry for JVM and clickView Details.
- Select theDashboards tab to see a static preview. If the dashboard is installed, then you can navigate to it by clickingView dashboard.
For more information about dashboards in Cloud Monitoring, seeDashboards and charts.
For more information about using theIntegrations page, seeManage integrations.
Install alerting policies
Alerting policies instruct Cloud Monitoring to notify you whenspecified conditions occur.The JVM integration includes one or more alerting policies foryou to use.You can view and installthese alerting policies from theIntegrations page inMonitoring.
To view the descriptions of available alerting policies and install them, do the following:
In the Google Cloud console, go to the
Integrations page:If you use the search bar to find this page, then select the result whose subheading isMonitoring.
- Locate the entry for JVM and clickView Details.
- Select theAlerts tab. This tab provides descriptions of available alerting policies and provides an interface for installing them.
- Install alerting policies. Alerting policies need to know where to send notifications that the alert has been triggered, so they require information from you for installation. To install alerting policies, do the following:
- From the list of available alerting policies, select those that you want to install.
In theConfigure notifications section, select one or more notification channels. You have the option to disable the use of notification channels, but if you do, then your alerting policies fire silently. You can check their status in Monitoring, but you receive no notifications.
For more information about notification channels, seeManage notification channels.
- ClickCreate Policies.
For more information about alerting policies in Cloud Monitoring, seeIntroduction to alerting.
For more information about using theIntegrations page, seeManage integrations.
What's next
For a walkthrough on how to use Ansible to install the Ops Agent, configurea third-party application, and install a sample dashboard, see theInstall the Ops Agent to troubleshoot third-party applications video.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-12-15 UTC.