Migrate dashboards

Learn how to migrate Splunk AppDynamics dashboards and validate their charts, metrics, visualizations, and operational behavior.

Migrate supported Splunk AppDynamics dashboards using Migration Tool, then review every chart, query, filter, unit, and unsupported widget before using the target dashboard operationally.

Automated conversion accelerates the migration but does not establish functional parity. Complex metric expressions and unsupported visualizations require manual treatment.

Prerequisites

Confirm that:

  • The dashboard inventory identifies the dashboards and widgets in the migration wave.

  • Approve Business Transaction naming and workflow rules.

  • Configure required Monitoring MetricSets, activate them, and confirm entitlement for the target dashboards. Follow the linked page for configuration and verification steps.

  • The source and destination connections pass their tests.

  • The owner of each source dashboard has reviewed and approved the dashboards and widgets to include in the migration wave, the target audience, and the required view or edit permissions.

  • The target telemetry includes the metrics and dimensions used by the dashboard.

Run the migration

  1. Follow New Migration Job.

  2. Select the approved source and destination connections.

  3. Select the Dashboards tab.

  4. Select only the dashboards approved for the migration wave.

  5. Review the migration summary and tag.

  6. Start the job.

  7. Review the job and artifact-level results in the Migration Jobs Dashboard.

  8. Open every created dashboard in Splunk Observability Cloud.

Review widget mappings

Splunk AppDynamics widget Target treatment

Time Series Graph

Time Series chart

Metric Value

Single Value chart

Gauge

Single Value chart with an applicable radial or secondary visualization

Text

Text chart

Image

Text chart containing an approved image reference

Event List

Events Feed

Pie Chart

Migration Tool partially migrates pie charts as Table charts. Validate manually because Splunk Observability Cloud does not provide an equivalent pie visualization.

Health List or Health Status

Migration Tool does not support direct migration; replace it with an approved supported visualization or document the accepted gap.

iFrame

No direct migration; replace with an approved link or another supported visualization

Funnel Analysis

No direct equivalent; define another operational view or accept the gap

Review metrics and SignalFlow

For every chart:

  1. Verify the target metric identity.

  2. Verify the service, environment, namespace, workflow, and instance filters.

  3. Verify aggregation, grouping, rollup, and time range.

  4. Verify P50, P90, P95, and P99 calculations where applicable. See Verify percentile calculations.

  5. Convert duration values when the source and target use different units. For example, use .scale(0.000001) when a nanosecond metric must display milliseconds.

  6. Verify missing-data and no-traffic behavior.

  7. Verify dashboard variables, links, labels, and permissions.

  8. Ensure that the final SignalFlow contains no hard-coded example or environment-specific values. Use dashboard variables or other supported configuration references for values that vary by service, environment, workflow, instance, detector, or threshold.

See Create and customize dashboards, Create charts, and Analyze incoming data using SignalFlow.

Verify percentile calculations

For each migrated chart that displays a latency percentile:

  1. Record the percentile used by the source widget, such as P50, P90, P95, or P99.

  2. Open the migrated chart and verify that it uses the corresponding percentile value:

    • P50 uses 50.

    • P90 uses 90.

    • P95 uses 95.

    • P99 uses 99.

  3. Confirm that the calculation uses the appropriate latency histogram or Monitoring MetricSet. For example, calculate P90 from a histogram with .percentile(pct=90).

  4. Verify that the service, environment, endpoint, workflow, and other filters select the intended request population.

  5. Verify the grouping. Calculate one percentile across the selected population when the source widget shows an aggregate, or group by the applicable dimension when the source shows separate values.

  6. Confirm that the displayed duration unit matches the source widget, such as milliseconds rather than nanoseconds.

  7. Use the same representative traffic and time range to compare the source and target charts. Confirm that their values and trends support the same operational interpretation.

Do not calculate a percentile from an average or from another pre-aggregated value unless the source widget intentionally uses that calculation.

Review known differences

  • External images load only when the source permits access from Splunk Observability Cloud. Verify security and cross-origin requirements.

  • Single Value charts do not reproduce every Splunk AppDynamics baseline or trend visualization.

  • Migration Tool partially migrates pie charts as Table charts, which require manual validation because Splunk Observability Cloud does not provide an equivalent pie visualization.

  • Migration Tool does not support Health List and Health Status widgets; use an approved replacement, retire them, or document an accepted gap.

  • Detector links must use a verified supported identifier and behavior.

  • Unsupported widgets require an approved replacement, retirement, or accepted gap.

Record every manual change and user-visible difference. Preserve recoverable target content before retrying a migration that can overwrite it.

Complete this task when every dashboard has a terminal migration result and an approved validation plan for Phase 5.