Enable OpenTelemetry in the Machine Agent
Reference information for enabling OpenTelemetry in the Machine Agent while retaining Splunk AppDynamics reporting.
Configure the Machine Agent to keep reporting to Splunk AppDynamics while it also sends OpenTelemetry data to Splunk Observability Cloud.
Prerequisites
Confirm that:
- The current migration wave includes the Machine Agent.
- The Machine Agent version, Java runtime, operating system, and deployment method support the required OpenTelemetry mode.
- You have the approved Machine Agent and OpenTelemetry packages.
- You have a ready Collector or approved direct-ingest route.
- You know the planned values for OpenTelemetry service and resource attributes
service.name,service.namespace, anddeployment.environment.name. - You have a maintenance window and rollback path.
Review the Machine Agent documentation for your installed release and use the version of the topic that matches your agent release.
Enable dual-signal mode
- Enable dual-signal mode using the setting for your Machine Agent release.
- Specify the required OpenTelemetry service and resource attributes.
- Set the OTLP endpoint and protocol for the selected Collector or direct-ingest route.
Verify the agent
- Generate representative traffic.
-
Verify that every application in the migration wave sends complete, correctly identified telemetry to Splunk Observability Cloud while Splunk AppDynamics monitoring remains available:
- The Machine Agent 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 Machine Agent version, effective dual-signal setting, validation time, and result in the migration-wave record.