Phase 5: validate and prepare for operations

Verify that migrated APM telemetry and configurations provide the required monitoring outcomes, operate both platforms long enough to identify material differences, and prepare operations teams for cutover.

Verify that migrated APM telemetry and configurations provide the required monitoring outcomes, operate both platforms long enough to identify material differences, and prepare operations teams for cutover.

Complete controlled component testing before beginning the sustained dual-platform validation period.

Prerequisites

Confirm that:

  • All in-scope applications send current telemetry to Splunk AppDynamics and Splunk Observability Cloud.
  • Business Transaction rules and required MetricSets are configured.
  • Supported Health Rules, dashboards, and notification integrations are migrated.
  • Nonportable and unsuccessful artifacts have an approved disposition or owner.
  • Representative traffic and an approved test method are available.
  • The dual-platform validation period and success criteria are documented.
  • Application, observability, operations, and change-approval owners are available.

Phase 5 tasks

Complete the tasks in order.

Task Purpose
Validate Migrated Telemetry and Configurations Test Business Transactions, detectors, dashboards, traces, service topology, notification integrations, and MetricSets. Complete the controlled-validation gate before sustained comparison.
Run Dual-Platform Validation Operate both platforms for the approved period and compare alerts, dashboards, telemetry, and topology under representative conditions.
Build Operational Confidence Have operations and on-call teams use Splunk Observability Cloud for priority investigation and response workflows.
Resolve Validation Gaps and Approve Cutover Readiness Resolve or formally accept identified gaps, consolidate evidence, and obtain the cutover decision.

Operational-confidence activities can run during the dual-platform validation period, but complete the controlled-validation gate before starting either activity.

Confirm readiness

Phase 5 is complete when:

  • The approved dual-platform validation period is complete.
  • Critical Business Transactions and services are visible.
  • Detectors and dashboards meet the approved accuracy criteria.
  • Trace, Service Map, notification, and MetricSet validation is complete.
  • Migration results are reconciled with the approved migration-wave inventory.
  • No critical or high-severity issue remains open.
  • Deferred items and accepted gaps have stakeholder approval.
  • Operations teams can complete priority workflows without undocumented assistance.
  • Runbooks, ownership, escalation paths, and support contacts are current.
  • Stakeholders approve the migration wave for cutover.

Continue to Phase 6: Cut Over and Stabilize.