Cut over the Node.js agent

Reference information for cutting over the Node.js agent from dual telemetry to Splunk Observability Cloud.

Use this procedure to stop the Node.js application from reporting to Splunk AppDynamics while preserving OpenTelemetry telemetry to Splunk Observability Cloud.

Prerequisites

Confirm that the Node.js application passed Phase 5 validation and that you have:

  • The installed Node.js Agent version, distribution method, and matching documentation.
  • A restorable copy of the last verified dual-signal configuration and package manifest.
  • The approved OpenTelemetry endpoint and service-identity values.
  • A change window, representative traffic, and an approved rollback procedure.

Select the cutover method approved for the application:

  • Switch the combined agent to OpenTelemetry-only mode. Use this method when the installed Node.js combined agent supports that mode.
  • Replace the combined agent with Splunk OpenTelemetry Node.js instrumentation. Use this method only when replacement is part of the approved deployment plan.

Switch the combined agent to OpenTelemetry-only mode

  1. Review Dual Signal Mode for Node.js Combined Agent, then select the documentation version that matches the installed Node.js Agent.
  2. Record the current initialization, package, environment-variable, OpenTelemetry route, and resource-attribute configuration.
  3. Change the documented deployment-mode setting from dual to otel. Use either the environment-variable method or the application-configuration method that the installed release supports.
  4. Keep the verified OpenTelemetry endpoint and service-identity values unchanged.
  5. Preserve the initialization order that the installed agent release requires.
  6. Restart or redeploy the application through the approved change process.
  7. Generate representative traffic and complete the post-cutover checks.

Do not configure the deployment mode in multiple locations with conflicting values.

Replace the combined agent

Use this method only when the approved design requires standalone Splunk OpenTelemetry Node.js instrumentation.

  1. Record the existing initialization order and preserve the rollback package and configuration.
  2. Confirm the supported Splunk OpenTelemetry Node.js distribution and version for the application runtime.
  3. Configure the approved OpenTelemetry endpoint and the same service-identity values that you validated during dual-platform operation.
  4. Remove the Splunk AppDynamics initialization and dependency, and initialize the approved Splunk OpenTelemetry instrumentation before application modules load.
  5. Confirm that only the intended Node.js automatic instrumentation initializes.
  6. Restart or redeploy the application, generate representative traffic, and complete the post-cutover checks.

If validation fails or you meet a rollback trigger, use Roll Back the Cutover.