A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://cloud.google.com/monitoring/agent/plugins/jvm below:

Standalone JVM Monitoring plugin | Google Cloud

Standalone JVM Monitoring plugin

Stay organized with collections Save and categorize content based on your preferences.

Cloud Monitoring can monitor Java Virtual Machine processes for common Java metrics.

This functionality is only available for agents running on Linux. It is not available on Windows.

Note: You can now collect metrics from your Java Virtual Machine instance using the Ops Agent, the primary and preferred agent for collecting telemetry from your Compute Engine instances. For details, see configuring the Ops Agent for JVM. Discovery

To see the metrics for Java Virtual Machine, do the following:

  1. In the Google Cloud console, go to the  Dashboards page:

    Go to Dashboards

    If you use the search bar to find this page, then select the result whose subheading is Monitoring.

  2. Select the Java Virtual Machine dashboard from the list.
Configuring Monitoring to monitor Java VMs Note: You do not have to install this plugin if you install one of the Java-based plugins listed in the Discovery section.

After you install the monitoring agent, use the following instructions to configure the JVM plugin on your instances.

Prerequisites

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.

On your VM instance, download jvm-sun-hotspot.conf from the GitHub configuration repository and place it in the directory /etc/stackdriver/collectd.d/:

(cd /etc/stackdriver/collectd.d/ && sudo curl -O https://raw.githubusercontent.com/Stackdriver/stackdriver-agent-service-configs/master/etc/collectd.d/jvm-sun-hotspot.conf)

As root, edit the downloaded configuration file and replace JMX_PORT by the port on which your JVM is configured to allow JMX connections.

After adding the configuration file, restart the monitoring agent by running the following command:

sudo service stackdriver-agent restart

For more information on the collectd GenericJMX plugin used to monitor the JVM, see Plugin:GenericJMX.

What is monitored

The full list of metrics the JVM plugin monitors is at Agent metrics: jvm.

Any additional JMX metrics (MBean attributes) must be sent to Cloud Monitoring as user-defined metrics. For more information, see User-defined metrics from the agent. Any user-supplied MBeans added to the configuration that are not redirected to user-defined metrics are rejected by the API.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-07 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4