Validate application telemetry in Splunk Observability Cloud

Reference information for validating application telemetry in Splunk Observability Cloud while Splunk AppDynamics SaaS monitoring remains available.

Verify that every application in the migration wave sends complete, correctly identified telemetry to Splunk Observability Cloud while Splunk AppDynamics SaaS monitoring remains available.

Use representative application traffic and repeat these checks for every application in the wave.

Consider dual-signal mode verified only after you confirm the effective configuration and current data at both destinations.

Validate the service and its dependencies

  1. In Splunk Observability Cloud, select APM, then Service map.
  2. Select the migration environment and a time range that includes the validation traffic.
  3. Find the expected service. If necessary, search by its approved service name.
  4. Confirm that expected upstream services, downstream services, databases, and external dependencies appear.
  5. Investigate unexpected or missing dependencies before continuing.

See View dependencies in the service map.

Validate traces

  1. In Splunk Observability Cloud, select APM, then Traces.
  2. Filter by the migration environment and service.
  3. Open a trace generated by the validation traffic.
  4. Confirm that the trace includes the expected root span, child spans, timing, errors, database calls, and outbound HTTP calls.
  5. Inspect the root span and verify the required attributes.

See Search traces using Trace Analyzer.

Verify identity and resource attributes

Attribute What to verify
appd.app.name Matches the Splunk AppDynamics application name.
appd.bt.name Identifies the originating Business Transaction when the agent provides it.
appd.request.guid Provides the Splunk AppDynamics transaction identifier when the agent provides it.
appd.tier.name Matches the Splunk AppDynamics tier name.
appdynamics.agent.version Identifies the combined-agent version.
deployment.environment.name Matches the Splunk AppDynamics account name.
service.instance.id Identifies the instance when required.
service.name Matches the Splunk AppDynamics tier name.
service.namespace

Matches the Splunk AppDynamics application name.

Note:

Set service.namespace and deployment.environment.name together. They provide the stable application and environment context used to find and validate the migrated services.
service.version Matches the service version when required. Add service.version when your service-version convention requires it.

Attribute availability can differ by agent type and release. Record an attribute as not applicable only when the current support documentation confirms that the agent does not provide it.

Validate both destinations

Confirm that:

  • You can view the service in Splunk Observability Cloud with the expected request, error, and duration data.
  • You can find representative traces and dependencies.
  • The service and environment attributes match the Phase 1 mapping.
  • Splunk AppDynamics SaaS continues to receive the expected data.
  • Agent and Collector logs do not show persistent export, queue, authentication, or connection errors.
  • Any missing or incorrect telemetry has an owner and resolution plan.

Record the evidence and result for each application in the migration wave.