Phase 2: Enable Dual Signal Mode

3. Verify in Both Platforms

With dual mode enabled and load flowing, traces should be arriving in Splunk Observability Cloud within a few minutes. Let’s verify both destinations.

Verify AppDynamics (Unchanged) #

Go back to the AppDynamics Controller ↗ , open your application, and confirm:

• The OrderService tier is still visible in the flow map
• Business transactions for /order and /inventory are still recording
• No errors or degradation from adding dual mode

Dual mode should not impact AppDynamics data collection both streams operate independently.

Verify Splunk Observability Cloud #

1. Navigate to Splunk Observability Cloud ↗ and log in with the credentials provided by your instructor.
2. Click APM in the left navigation panel.
3. In the Environment dropdown, select <INSTANCE>-appd-dual (this matches the deployment.environment value you set in the resource attributes).

   

4. You should see OrderService in the service list.

Explore a Trace #

1. Click on the OrderService service.
2. Click Traces to view individual traces.
3. Select a trace for GET /order to open the trace detail waterfall.

In the trace waterfall, you’ll see spans generated by the OTel Java auto-instrumentation. These are the same requests that AppDynamics is also monitoring.

Examine the AppDynamics Correlation Attributes #

Click on a root span and look at the span attributes. You should see the AppDynamics correlation attributes:

These attributes are automatically added by the AppDynamics agent in dual mode. They create a direct link between this OTel trace and the corresponding data in the AppDynamics Controller.

You now have the same application sending APM data to two platforms simultaneously from a single agent. In the next section, you’ll connect the two by creating a global data link.