The "Code Hotspots" tab within a trace view integrates data from the Datadog Continuous Profiler. The profiler analyzes code-level execution and can identify performance bottlenecks, including time spent waiting for the garbage collector (GC). This information is presented in a flame graph, allowing you to see precisely which methods are consuming CPU or wall time, with GC activity being one of the identifiable sources of latency.

A. The Infrastructure tab correlates the trace with host-level metrics (CPU, memory), not application-specific GC time for that trace.

B. The Network tab shows TCP-level metrics for the request and is unrelated to the application's internal memory management or GC.

C. The Processes tab lists running processes on the host but does not provide a detailed breakdown of GC time for a specific trace.

- Datadog Documentation, "Continuous Profiler > Explore Profiles". This page notes: "The profiler is able to distinguish time spent on CPU, waiting for I/O, waiting for locks, and other time sinks such as garbage collection."

- Datadog Documentation, "APM > Traces > Trace View". The documentation describes the integration of Profiler data into the trace view under tabs like "Code Hotspots" to pinpoint performance issues.