Prepare for cutover

Confirm that a migration wave meets its readiness criteria before you stop Splunk AppDynamics SaaS reporting and continue OpenTelemetry reporting to Splunk Observability Cloud.

Overview

Use this procedure to confirm that a migration wave is ready to stop reporting to Splunk AppDynamics SaaS while continuing to report OpenTelemetry data to Splunk Observability Cloud.

Prerequisites

Complete Phase 5 validation for the migration wave. Do not start cutover until the application owner, migration owner, and operations owner approve the results.

Confirm that the approved change record identifies:

  • The applications and agent instances in the wave.
  • The cutover window and execution order.
  • The person authorized to start or stop the change.
  • The rollback triggers and rollback decision owner.
  • The runtime-specific cutover procedure for each application.
  • The saved agent and Collector configuration required for rollback.

Complete the final readiness check

Area Confirm
Telemetry Required services, operations, dependencies, traces, and metrics are visible in Splunk Observability Cloud.
Service identity Service names, namespaces, deployment environments, and other required resource attributes use the approved values.
Monitoring Required dashboards and detectors are validated, and notification routes are tested.
Comparison Latency, throughput, and error-rate results meet the success criteria approved for the wave.
Coverage No required services or endpoints are missing, and trace sampling provides sufficient coverage for validation.
Operations Runbooks, incident-response procedures, escalation paths, and Support contacts are current.
People Application owners, observability administrators, change approvers, and on-call responders are available for the cutover window.
Recovery The last verified dual-signal configuration, packages, deployment manifests, and alert-routing settings can be restored.

Do not proceed while a critical issue, an unmet success criterion, or an unresolved rollback trigger remains.

Record the cutover plan

For each application, record:

  1. The current agent type, version, and deployment method.
  2. Whether you switch a combined agent to OpenTelemetry-only mode or replace it with standalone Splunk OpenTelemetry instrumentation.
  3. The exact configuration change from the documentation for the installed agent version.
  4. The OpenTelemetry endpoint, protocol, and service-identity values that must remain unchanged.
  5. The traffic or transaction that you use for validation.
  6. The expected time for telemetry and Splunk AppDynamics reporting changes to appear.
  7. The rollback command or deployment action and its owner.

Proceed with the runtime-specific procedure

Use the Java, .NET, or Node.js cutover page for each application in the wave. Apply the change to only the approved wave, then complete post-cutover validation before expanding the cutover.