Enable OpenTelemetry in the Node.js agent

Configure the Node.js combined 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 Node.js application.
• The Node.js runtime, application framework, agent version, and deployment method support the required OpenTelemetry mode.
• You have the approved Node.js 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, and deployment.environment.name.
• You have a maintenance window and rollback path.

Review Enable OpenTelemetry in the Node.js Agent and use the version of the topic that matches your agent release.

Enable dual-signal mode

1. Make the Splunk AppDynamics require and profile call the first instrumentation statement in the application's entry point.
2. Enable dual-signal mode using the setting for your Node.js Agent release. See Enable Dual-Signal Mode (Nodejs), and select the documentation version that matches your Splunk AppDynamics Controller version.
3. Specify the required OpenTelemetry service and resource attributes.
4. Set the OTLP endpoint and protocol for the selected Collector or direct-ingest route.

Verify the agent

1. Generate representative traffic.
2. Verify that the Splunk AppDynamics require and profile call runs before other instrumentation.

3. 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 Node.js Agent version, effective dual-signal setting, validation time, and result in the migration-wave record.