Validate and stabilize after cutover
Validate applications after cutover and monitor the migration wave through its approved stabilization period.
Overview
Validate each application immediately after cutover, then monitor the migration wave through the approved stabilization period before retiring superseded monitoring.
Validate immediately
Generate representative traffic and confirm:
| Check | Expected result |
|---|---|
| Telemetry flow | Splunk Observability Cloud continues to receive current traces and metrics. |
| Cutover scope | Splunk AppDynamics reporting stops only for the applications included in the approved wave. |
| APM topology | Required services and dependencies remain visible in the APM Service Map. |
| Operations | Critical operations and workflows remain visible with the approved names. |
| Monitoring | Dashboards display current data, detectors continue to evaluate, and notification routes deliver test alerts to the intended recipients. |
| Application behavior | Latency, throughput, error rate, and resource use remain within the approved limits. |
| Telemetry health | Agent and Collector logs show no unresolved export, authentication, connectivity, or configuration errors. |
| Investigation | Required dimensions and indexed span tags continue to support dashboard filtering and trace investigation. |
If a check fails, determine whether an approved rollback trigger has occurred. Stop expanding the cutover until you resolve the problem or roll back the affected application.
Monitor the stabilization period
Observe the wave for at least 72 hours after cutover, or for the longer period required by the approved migration plan. During this period:
- Monitor telemetry completeness and application health.
- Review detector accuracy and notification delivery.
- Track agent and Collector resource use.
- Investigate missing services, traces, operations, or dimensions.
- Keep the rollback owner and on-call team available.
- Record incidents, workarounds, and documentation gaps.
- Do not add another wave while the current wave has a critical unresolved issue.
Use the Migration Analytics Dashboard to review migration-job activity. Use operational validation results, application evidence, and change records, not aggregate artifact counts, to approve the cutover.
Complete stabilization
Complete stabilization after you verify:
- No critical issue occurred during the approved observation period.
- Telemetry and monitoring meet the wave’s success criteria.
- Application and operations owners approve the results.
- No active rollback trigger remains.
- Record evidence and decisions in the migration record.
After approval, continue to Retire Superseded Splunk AppDynamics Monitoring.