Phase 3: enable application telemetry

Use Phase 3 to configure a Splunk AppDynamics Combined Agent in dual-signal mode. This mode sends OpenTelemetry application data to Splunk Observability Cloud while also continuing to send application data to Splunk AppDynamics. This page is the start of the workflow for setting up the combined agent in dual-signal mode.

Use Phase 3 to configure a Splunk AppDynamics Combined Agent in dual-signal mode. This mode sends OpenTelemetry application data to Splunk Observability Cloud while also continuing to send application data to Splunk AppDynamics. This page is the start of the workflow for setting up the combined agent in dual-signal mode.

The combined agent uses two independent reporting paths:

  • The Splunk AppDynamics reporting path continues to send data to Splunk AppDynamics through the existing Controller configuration.
  • The OpenTelemetry reporting path sends telemetry to Splunk Observability Cloud through the selected telemetry route.

Overview

Configure the combined agent for each in-scope application to send data to both Splunk AppDynamics and Splunk Observability Cloud.

Keep the combined agent in dual-signal mode throughout this phase. Dual-signal mode lets you establish and validate monitoring in Splunk Observability Cloud without interrupting existing Splunk AppDynamics monitoring. Do not configure the combined agent in Splunk AppDynamics-only mode or OpenTelemetry-only mode during Phase 3. Select OpenTelemetry-only mode during cutover only after the application passes the required validation.

Prerequisites

Confirm that:

  • Phase 2 is complete.
  • The application inventory identifies the agent type and deployment method for every application in the migration wave.
  • The deployment owner can retrieve the approved combined-agent and rollback packages for every in-scope runtime, operating system, and architecture. See Confirm Package Availability.
  • Application owners have approved service names, namespaces, and environment values.
  • Change approvals, maintenance windows, and rollback procedures are ready.
  • Application owners can generate or identify representative traffic.

Confirm package availability

Confirm that the target package is available for the agent required for the application.

Deployment method Verification
Smart Agent In the Controller, select Home > Agent Management > Manage Agents. Confirm that the target host appears in the Smart Agent inventory. Start the installation or upgrade workflow and verify that you can select the approved agent type, version, target host, and download source. Exit the workflow without submitting the task. See Manage the Agents Using UI.
Existing deployment process Confirm that the approved package exists in the artifact repository or package source. Verify that the pipeline identity can retrieve it and that it matches the required runtime, operating system, and architecture. Validate its checksum or digital signature when available. See Download Splunk AppDynamics Software.

For each package, record:

  • Agent type and approved version.
  • Target operating system and architecture.
  • Package source or repository location.
  • Checksum or signature-validation result, when available.
  • Deployment owner.
  • Corresponding rollback package and version.

Do not consider the package available only because it appears in a repository or catalog. Confirm that the actual deployment identity can retrieve it.

Complete the phase 3 tasks

Complete only the agent-specific pages that apply to the applications in the migration wave.

  1. Set Up the Splunk Distribution of the OpenTelemetry Collector: The selected local or gateway route can receive OTLP telemetry and export it to the destination organization. Skip this task only if you've been approved for the direct ingest option.
  2. Generate and review an application configuration: For each supported application, generate a configuration, review it, and prepare it for deployment through the approved process.
  3. Enable OpenTelemetry in the Java Agent: In-scope Java applications run the combined agent in dual-signal mode and use the selected telemetry route.
  4. Enable OpenTelemetry in the .NET Agent: In-scope .NET applications run the combined agent in dual-signal mode and use the selected telemetry route.
  5. Enable OpenTelemetry in the Node.js Agent: In-scope Node.js applications run the combined agent in dual-signal mode and use the selected telemetry route.
  6. Validate Application Telemetry in Splunk Observability Cloud: Services, dependencies, traces, and required attributes are correct for every application in the migration wave.
  7. Assess the Performance Impact: Each application meets its approved performance criteria or has an approved exception.

Confirm readiness

Confirm that:

  • [ ] Every application in the migration wave uses an approved telemetry route.
  • [ ] Generated configurations have been reviewed, deployed, and reconciled with the approved service identity and Collector deployment option.
  • [ ] Dual-signal mode has been verified for every application. See Validate application telemetry in Splunk Observability Cloud.
  • [ ] Splunk AppDynamics and Splunk Observability Cloud both receive the expected data.

  • [ ] You reviewed the applicable agent and Collector logs and resolved any persistent initialization, authentication, connection, queue, dropped-data, or export errors. See Troubleshoot your instrumentation.

  • [ ] Performance remains within the application-specific limits approved for the migration wave.
  • [ ] Application and migration owners approve the Phase 3 results.

Keep dual-signal mode enabled until the monitoring configurations and operational workflows required for cutover have been validated.

After Phase 3 is approved, continue to Phase 4: Migrate Monitoring Configurations.