Service Flow vs Transaction Tracing: Trading Service-Level Overview for Call-Stack Precision Under Custom Instrumentation

In recent Dynatrace versions, when a latency spike appears in an application that uses custom instrumentation, the immediate goal is to isolate whether the delay sits at a service boundary or inside a specific code path. Transaction Tracing provides per-transaction call stacks, SQL statements, and HTTP calls, but it carries higher CPU and memory overhead and may require sampling under high throughput. Service Flow offers an aggregated view of inter-service communication and latency hotspots, yet its completeness depends on Automatic Service Detection, which can misclassify services when custom instrumentation is present and produce incomplete topology graphs.

This creates an unresolved trade-off: accept a potentially partial Service Flow diagram to keep overhead low, or enable targeted Transaction Tracing sessions to capture exact call stacks despite the performance cost. The uncertainty deepens when missing services in the flow cannot be confirmed without cross-referencing application logs or manual service mapping.

Which documented approach should be prioritized first when Automatic Service Detection yields an incomplete Service Flow? How should the choice between Transaction Tracing overhead and Service Flow topology gaps be evaluated for a high-throughput, custom-instrumented service? What verification steps can confirm that the selected view actually captures the true bottleneck without introducing measurement distortion?