Retire superseded Splunk AppDynamics monitoring

Retire Splunk AppDynamics monitoring for a migration wave only after the migration wave completes post-cutover stabilization and the application and operations owners approve the result.

Prerequisites

Confirm that:

• Every application in the wave reports through the approved OpenTelemetry-only path.
• The approved stabilization period ends.
• No critical issue or active rollback trigger remains.
• Splunk Observability Cloud dashboards, detectors, and notification routes are operational.
• You document historical-data access and retention requirements.
• The rollback owner confirms that the retiring configuration no longer supports immediate recovery.

Retire monitoring for the wave

1. Turn off Splunk AppDynamics Health Rules, policies, and actions that alert on the migrated applications.
2. Confirm that Splunk Observability Cloud owns the active alert and notification route for each operational condition.
3. Retire superseded Splunk AppDynamics dashboards, deep links, and operational references according to the approved retention policy.
4. Remove obsolete Splunk AppDynamics agent settings, packages, and deployment steps only through the approved change and software-retirement process.
5. Revoke temporary migration credentials when their approved retention period ends.
6. Update application inventory, ownership, runbooks, incident-response procedures, and Support records.
7. Preserve access to required historical Splunk AppDynamics data for the agreed retention period.
8. Record the final application-owner, operations-owner, and migration-owner approval.

Completion criteria

The migration wave is complete when:

• You turn off Splunk AppDynamics ingestion and alerting for the wave.
• Applications use the approved OpenTelemetry-only configuration.
• Splunk Observability Cloud receives reliable telemetry and supports the required operational workflows.
• You document historical-data retention and access.
• You record all retirement actions and final approvals.