Resolve validation gaps and approve cutover readiness

Use validation results to resolve or accept material issues and approve migration-wave readiness for cutover.

Overview

Resolve or formally accept every material issue identified during controlled testing and dual-platform validation before approving the migration wave for cutover.

Consolidate the validation results

Create one validation record for the migration wave. Include:

  • Controlled component-test results.
  • Alert comparison log.
  • Dashboard comparison results.
  • Trace and Service Map findings.
  • Notification test results.
  • MetricSet validation results.
  • Operational practice results.
  • Migration-job and artifact outcomes.
  • Open issues, accepted differences, and supporting evidence.

Reconcile the Migration Analytics Dashboard and Migration Jobs Dashboard with the approved migration-wave inventory.

Classify each gap

Gap category Examples
Data gap Missing metric, trace, service, span, dimension, or dependency
Data-accuracy gap Material difference in metric value, percentile, unit, rollup, or scope
Alert gap Missed alert, false positive, incorrect severity, timing difference, or notification failure
Configuration gap Incorrect detector, dashboard, rule, MetricSet, filter, or integration
Feature gap Required Splunk AppDynamics capability has no direct target equivalent
Operational gap Missing permission, runbook, training, ownership, or escalation path
Migration-processing issue Failed, partial, warning, pending, or incorrectly overwritten artifact

For nonportable or unsuccessful artifacts, follow Resolve Nonportable or Unsuccessful Artifacts.

Assign a treatment

For each gap:

  1. Record the affected application, configuration, monitoring outcome, evidence, and severity.
  2. Assign an owner and due date.
  3. Select the treatment: correct and retest, recreate manually, rebuild, replace, defer, retire, or accept the gap.
  4. Assess the operational effect and cutover risk.
  5. Obtain the required approval for deferred work or an accepted gap.
  6. Retest corrected items using the original validation method.
  7. Close the item only after recording the result and evidence.

Resolve critical and high-severity issues before cutover. Do not use a lower aggregate match rate to conceal a missed critical alert, service, or workflow.

Review audit evidence when required

If the change-control or audit process requires evidence, review the applicable Report, Configuration, and Migration entries in Audit Logs. Reconcile the entries with migration-job results and the configurations deployed in Splunk Observability Cloud.

Conduct the cutover-readiness review

Review the following with the migration owner, application owners, observability administrators, operations owners, and change approver:

  • Approved validation period and results.
  • Business Transaction and service coverage.
  • Detector accuracy and notification delivery.
  • Dashboard accuracy and usability.
  • Trace and dependency coverage.
  • Outstanding defects and deferred work.
  • Accepted differences and risks.
  • Operational readiness and runbook status.
  • Cutover plan, rollback triggers, and decision owner.
  • Required support coverage.

Record the decision, approvers, conditions, and date.

Phase 5 completion criteria

Phase 5 is complete when:

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