Phase 6: cut over and stabilize

Use Phase 6 to move an approved migration wave from dual-platform monitoring to OpenTelemetry-only monitoring in Splunk Observability Cloud. Cut over only the applications in the approved wave, validate them immediately, and observe them through the stabilization period before retiring superseded Splunk AppDynamics monitoring.

Use Phase 6 to move an approved migration wave from dual-platform monitoring to OpenTelemetry-only monitoring in Splunk Observability Cloud. Cut over only the applications in the approved wave, validate them immediately, and observe them through the stabilization period before retiring superseded Splunk AppDynamics monitoring.

Prerequisites

Confirm that:

  • Phase 5 validation is complete for the wave.
  • The wave meets its approved success criteria and has no critical blockers.
  • Application, migration, operations, and change owners approved the cutover.
  • The cutover window, execution order, communications, and on-call coverage are confirmed.
  • Rollback triggers, the rollback decision owner, and restorable configurations are available.

Cutover methods

The approved method can differ by runtime and deployment. Use the documentation for the installed agent release.

Runtime Documented methods in this phase
Java Switch a supported combined agent to OpenTelemetry-only mode, or replace it with approved Splunk OpenTelemetry Java instrumentation.
.NET Switch a supported .NET combined agent from dual to otel. This help does not define a generic .NET combined-agent replacement procedure. If the combined agent is not supported, use the independent OpenTelemetry instrumentation path approved for the migration wave.
Node.js Switch a supported combined agent to OpenTelemetry-only mode, or replace it with approved Splunk OpenTelemetry Node.js instrumentation.

Changing the combined-agent mode changes the application telemetry path. Keep the verified OpenTelemetry endpoint and service-identity settings unless the approved cutover plan requires a separate change.

Complete phase 6

Complete the topics in this order:

Step Topic Outcome
1 Prepare for Cutover Confirm readiness, approvals, scope, and rollback capability.
2 Cut Over the Java Agent Apply the approved Java cutover method.
2 Cut Over the .NET Agent Switch a supported .NET combined agent to Splunk-only mode.
2 Cut Over the Node.js Agent Apply the approved Node.js cutover method.
3 Validate and Stabilize After Cutover Verify telemetry, monitoring, application health, and operational stability.
As required Roll Back the Cutover Restore the last verified dual-signal configuration when a rollback trigger is met.
4 Retire Superseded Splunk AppDynamics Monitoring Retire Splunk AppDynamics ingestion and monitoring after stabilization and approval.

For applications that use different runtimes, apply the corresponding approved instrumentation procedure and the same readiness, validation, rollback, and stabilization controls.

Phase completion criteria

Phase 6 is complete for the migration wave when:

  • Splunk AppDynamics ingestion and alerting are deactivated for the applications in the wave.
  • Applications use their approved OpenTelemetry-only configuration.
  • Splunk Observability Cloud receives reliable telemetry and supports the required dashboards, detectors, notifications, and investigation workflows.
  • Application performance remains within the approved limits throughout the stabilization period.
  • Historical Splunk AppDynamics data access and retention are documented.
  • Application, operations, and migration owners approve the completed cutover.