When you are connected to the profiled application, use the "Threads" tab to track the live threads.
A very useful and unique feature of this graph is that the telemetry information is remembered inside the profiler agent. This allows you to connect to the profiled application on demand and discover how the application behaved in the past.
Please also consider the automatic deadlock detector
Disabling/enabling stack telemetry
The thread stack and state telemetry information can be very useful because it allows you to connect to the profiled application on demand and discover how the application behaved in the past. In most cases, there is no significant overhead of collecting this information, and thus you do not need to disable it.
However, it makes sense to disable it in production J2EE servers in order to ensure minimum profiling overhead.
The telemetry is enabled by default, unless "disablestacktelemetry" startup option was specified.
When you are connected to the profiled application, use corresponding toolbar button to enable/disable the telemetry:
