Problem: Call graphs aren't visible

Java, .NET

In asynchronous, event-driven environments, sampled traces may occasionally lack call stack data. This is expected behavior and typically occurs when the application is waiting for external operations such as:

• Awaiting a remote service response over HTTP or gRPC.

• Application logic executing entirely between sampling intervals.

During these periods, no user code is actively executing. If the snapshot profiler samples during such a gap, no stack is captured. As a result, even a successfully processed request may appear without call graph data.

This behavior reflects the limitations of sampling-based profiling and does not indicate a misconfiguration.

Node.js

In asynchronous, event-driven environments, sampled traces may occasionally lack call stack data. This is expected behavior and typically occurs when the application is waiting for external operations such as:

• Database queries

• Upstream service responses

• Timers (e.g., setTimeout, setInterval)

During these periods, no user code is actively executing. If the snapshot profiler samples during such a gap, no stack is captured. As a result, even a successfully processed request may appear without call graph data.

This behavior reflects the limitations of sampling-based profiling in non-blocking runtimes and does not indicate a misconfiguration.