Java metrics 🔗

The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the java-monitor to retrieve metrics from a Java application.

This integration is available on Linux and Windows.

Note

To activate metrics collection in the OpenTelemetry Java agent, see Activate metrics collection.

Benefits 🔗

After you configure the integration, you can access these features:

View metrics. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. For information about dashboards, see View dashboards in Splunk Observability Cloud.
View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Use navigators in Splunk Infrastructure Monitoring.
Access the Metric Finder and search for metrics sent by the monitor. For information, see Search the Metric Finder and Metadata catalog.

Follow these steps to deploy this integration:

Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:
Configure the monitor, as described in the Configuration section.
Restart the Splunk Distribution of OpenTelemetry Collector.

To use this integration of a Smart Agent monitor with the Collector:

Include the Smart Agent receiver in your configuration file.
Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

To activate this integration, add the following to your Collector configuration:

receivers:
  smartagent/java-monitor:
    type: java-monitor
    ... # Additional config

Next, add the monitor to the service.pipelines.metrics.receivers section of your configuration file:

service:
  pipelines:
    metrics:
      receivers: [java-monitor]

The following table shows the configuration options for the java-monitor:

Option	Required	Type	Description
`host`	no	`string`	Host is filled in by auto-discovery if the receiver has a discovery rule.
`port`	no	`integer`	Port is filled in by auto-discovery if the receiver has a discovery rule. Default value is `0`.
`jarFilePath`	no	`string`	Path to the jar file that implements the monitoring logic.
`javaBinary`	no	`string`	By default, the agent use its bundled Java runtime (Java 8). If you wish to use a Java runtime that already exists on the system, specify the full path to the `java` binary here in `/usr/bin/java`.
`mainClass`	no	`string`	The class within the specified `jarFilePath` that contains a main method to execute.
`classPath`	no	`list of strings`	Additional class paths to set on the invoked Java subprocess.
`extraJavaArgs`	no	`list of strings`	Additional flags to the Java subprocess

The following metrics are available for this integration:

To learn more about the available in Observability Cloud see Metric types.
In host-based subscription plans, default metrics are those metrics included in host-based subscriptions in Observability Cloud, such as host, container, or bundled metrics. Custom metrics are not provided by default and might be subject to charges. See Metric categories for more information.
In MTS-based subscription plans, all metrics are custom.
To add additional metrics, see how to configure extraMetrics in Add additional metrics.

If you are not able to see your data in Splunk Observability Cloud, try these tips:

Submit a case in the Splunk Support Portal.
- Available to Splunk Observability Cloud customers
Call Splunk Customer Support
- Available to Splunk Observability Cloud customers
Ask a question and get answers through community support at Splunk Answers.
- Available to Splunk Observability Cloud customers and free trial users
Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide
- Available to Splunk Observability Cloud customers and free trial users
- To learn how to join, see Get Started with Splunk Community - Chat groups.

To learn about even more support options, see Splunk Customer Success.