Phase 4: migrate monitoring configurations

Use Phase 4 to align application operations and migrate the monitoring configurations required for the approved migration wave.

Use Phase 4 to align application operations and migrate the monitoring configurations required for the approved migration wave.

Overview

Compare Splunk AppDynamics Business Transactions with Splunk Observability Cloud operations, configure the required operation, endpoint, and workflow rules, create required MetricSets, and migrate supported dashboards, Health Rules, and HTTP Request Templates.

Automated migration accelerates configuration transfer, but it does not guarantee exact parity or operational correctness. Review every migrated artifact, document user-visible differences, and assign an approved treatment to failed, partial, unsupported, or nonportable items.

Prerequisites

Before beginning Phase 4, confirm that:

  • [ ] Phase 3 is complete for the migration wave.
  • [ ] Every in-scope application sends representative traces and metrics to Splunk Observability Cloud while Splunk AppDynamics monitoring remains available.
  • [ ] The source and destination Migration Tool connections pass their connection tests.
  • [ ] The application inventory includes the Business Transactions, detection rules, Health Rules, dashboards, HTTP Request Templates, custom metrics, and notification dependencies in scope.
  • [ ] Service identity and environment attributes match the approved migration inventory.
  • [ ] Configuration owners, application owners, dashboard owners, detector owners, and integration owners are assigned.
  • [ ] Log in to the destination organization as an administrator. Confirm that you can access Settings > APM & RUM MetricSets. You need the administrator role to index span attributes and create custom MetricSets.
  • [ ] Go to Settings > Subscription Usage or Settings > Billing and Usage, select APM, and review the current usage and subscription limits for Troubleshooting MetricSets and Monitoring MetricSets. You need the administrator or usage role to view these limits.
  • [ ] Recoverable copies or records exist for target artifacts that might be overwritten during a retry.

Complete the phase 4 tasks

Complete the following tasks in order.

Configure operation grouping and endpoint rules only when the Business Transaction analysis identifies a need.

  1. Analyze Business Transaction Compliance: Compare Splunk AppDynamics Business Transactions with target operations and assign a treatment to every important difference.
  2. Configure Operation Grouping Rules: Group operations with approved common prefixes when grouping reduces cardinality without hiding important operational distinctions.
  3. Configure Endpoint Rules: Rename or consolidate endpoints when targeted endpoint metrics and consistent transaction monitoring require it.
  4. Configure Workflow Rules: Align critical operation display names and sf_workflow values with the approved monitoring model.
  5. Configure MetricSets: Index the bounded span attributes required by dashboards, detectors, alerting, and troubleshooting.
  6. Migrate Dashboards: Migrate approved dashboards and review every target chart, query, filter, unit, visualization, and unsupported widget.
  7. Migrate Health Rules to Detectors: Migrate approved Health Rules and review the target SignalFlow logic, thresholds, scope, severity, timing, and notification behavior.
  8. Migrate HTTP Request Templates to webhook integrations: Migrate approved templates and review payload variables, transport security, routing, and unsupported source behavior.
  9. Resolve Nonportable or Unsuccessful Artifacts: Assign dispositions, resolve failures and partial results, preserve recoverable target content, and define replacement workflows.

After migration jobs reach a terminal state, review the Migration Analytics Dashboard for aggregate progress. Use the Migration Jobs Dashboard for artifact-level results and errors, and use Audit Logs when recorded activity, ownership, and timestamps are required.

A migrated count confirms that Migration Tool processed an artifact. It does not confirm that the resulting configuration provides the required monitoring outcome. Complete functional validation in Phase 5.

Confirm readiness

Confirm that:

  • [ ] Every critical Business Transaction has a corresponding target operation or an approved treatment.
  • [ ] Required operation grouping, endpoint, and workflow rules are configured and verified.
  • [ ] Required MetricSets are active and provide the approved dimensions.
  • [ ] Every selected dashboard, Health Rule, and HTTP Request Template has a terminal artifact-level result.
  • [ ] Every migrated dashboard, detector, and webhook integration has been reviewed.
  • [ ] Every failed, partial, unsupported, or nonportable item has an approved disposition, owner, and validation method.
  • [ ] Target artifacts affected by retries or overwrites are reconciled.
  • [ ] Historical-access, replacement-workflow, and accepted-gap decisions are documented.
  • [ ] Aggregate analytics results are reconciled with the migration-wave inventory.
  • [ ] No critical configuration-migration issue lacks an owner or approved treatment.
  • [ ] Application, configuration, and migration owners approve the Phase 4 results.

After completing these checks, continue to Phase 5: Validate and Prepare for Operations.