Enable OpenTelemetry in the Java agent

Configure the Java combined agent to keep reporting to Splunk AppDynamics while it also sends OpenTelemetry data to Splunk Observability Cloud.

For installation, compatibility, configuration properties, and dual-signal behavior, follow the agent documentation for the installed release. This migration page contains only migration-specific prerequisites, validation, and rollback guidance. Agent documentation provides the source of truth for agent configuration.

Prerequisites

Confirm that:

• The current migration wave includes the Java application.
• The Java agent, JVM, application framework, and deployment method support dual-signal mode.
• You have an approved combined-agent package and a rollback package. Check the current requirements and configuration properties in Enable OpenTelemetry in the Java Agent. Use the version of the topic that matches your agent release.
• Your environment has a Collector or approved direct-ingest route ready.
• You know the planned values for OpenTelemetry service and resource attributes service.name, service.namespace, and deployment.environment.name.
• You have a maintenance window and representative traffic for validation.

Enable dual-signal mode

1. Enable dual-signal mode using the setting for your Java Agent release. See Enable Dual Signal mode, and select the documentation version that matches your Splunk AppDynamics Controller version.

   Important:

   Note: Don’t specify the required OpenTelemetry service and resource attributes; the Java combined agent does this by default.

2. Depending on where your Collector is running, you might need to set the OTLP exporter endpoint and protocol for the selected Collector or direct-ingest route. See Install and activate the Java agent.

Verify the agent

1. Generate representative traffic.

2. Verify that every application in the migration wave sends complete, correctly identified telemetry to Splunk Observability Cloud while Splunk AppDynamics monitoring remains available:

   • The application starts normally.
   • The agent startup logs confirm that the Splunk AppDynamics and OpenTelemetry components initialize successfully without persistent configuration, exporter errors, or duplicate OpenTelemetry instrumentation.
   • The application reports data to both destinations during the same time period:
     • In Splunk AppDynamics, the expected application and tier receive current data.
     • In Splunk Observability Cloud, the expected services and their dependencies appear in the Service map, the expected traces receive current data, and the expected identity and resource attributes match the migration plan.

Next step

Record the Java Agent version, effective dual-signal setting, validation time, and result in the migration-wave record.