Wrap Up

Summary, cleanup, and next steps.

5 minutes

What You Accomplished

In this workshop you:

  1. Built and ran a Java service with normal AppDynamics instrumentation: a single agent sending APM data to the AppDynamics Controller only.

  2. Learned the difference between hybrid and dual signal mode: hybrid reuses AppD’s own instrumentation to generate OTel spans (lower overhead, narrower coverage), while dual runs the full OTel Java auto-instrumentation alongside AppD (broader coverage, adds correlation attributes).

  3. Enabled dual signal mode: by adding four JVM flags to the same process. No code changes, no second agent, no recompilation. The same AppDynamics agent now sends data to both AppDynamics and Splunk Observability Cloud simultaneously.

  4. Created a global data link: in Splunk Observability Cloud that uses the appd.* span attributes to navigate directly to the corresponding AppDynamics tier view.

Cleanup

Stop the application and load generator:

bash
kill %2 2>/dev/null   # load generator
kill %1 2>/dev/null   # java app

Optionally stop the collector:

bash
sudo systemctl stop splunk-otel-collector

Key Takeaways

Further Reading