Preview: Splunk Zero Config Auto Instrumentation
Preview features described in this document are provided by Splunk to you “as is” without any warranties, maintenance and support, or service-level commitments. Splunk makes this preview feature available in its sole discretion and may discontinue it at any time. Use of preview features is subject to the Splunk General Terms .
Splunk OpenTelemetry Zero Configuration Auto Instrumentation for Java 🔗
Splunk OpenTelemetry (OTel) Zero Configuration Auto Instrumentation for Java automatically instruments supported Java libraries in running applications to capture distributed traces. The Splunk OpenTelemetry Collector receives the distributed traces and forwards them to Splunk Application Performance Monitoring (APM) in Splunk Observability Cloud.
This feature provides the following benefits:
You don’t need to configure or manually instrument your applications before deployment if your Java applications use any of the supported libraries.
You can start streaming traces and monitor distributed applications with Splunk APM in minutes.
Automatic instrumentation is only available for applications using supported Java libraries. See Supported libraries and frameworks. If your application isn’t supported, manually instrument your service to generate trace data. See Manually instrument Java applications for Splunk Observability Cloud .
Your Splunk Observability Cloud realm and access token.
To get an access token, see Retrieve and manage user API access tokens using Splunk Observability Cloud.
To find the realm name of your account, open the navigation menu in Splunk Observability Cloud. Select Organizations section., and then select your username. The realm name appears in the
Zero Config Auto Instrumentation is available on Kubernetes and Linux using the Splunk OTel Collector and OTel Java agent. When you activate Zero Config, the Splunk OTel Java agent automatically instruments all Java applications running in the target environment.
On Linux, the target environment is the entire Linux host, so the Java agent instruments every Java application on the host.
On Kubernetes, the target environment is the deployment or pod where you activated instrumentation. The Java agent instruments every Java application within the pod or deployment.
In both cases you must restart the applications to start instrumentation.
You can also use the Kubernetes Operator for Auto Instrumentation. See an example in Scenario: Deploy the OpenTelemetry Operator and Java auto-instrumentation.
Follow the instructions from the following list:
Instrumentation sends trace data to Splunk APM. Learn what you can do with Splunk APM.
Learn more about the features of the Splunk Distribution of OpenTelemetry Java.