To view the thread profile details: Go to rpm.newrelic.com/apm or rpm.newrelic.com/browser > Key transactions > (select a key transaction) > x-ray > (select an x-ray session) > Thread profile. The selected x-ray session's Thread Profile page lists the total sample count. From here you can drill down into tree view details and change the settings for the thread profile results.
Access to this feature depends on your subscription level.
The Thread Profile page shows a tree view of the call stacks, which you can collapse or expand. The page also includes summary information about the date, duration, process, and user name. By default the tree view shows call stacks in the standard parent-child (top down) order. To change this, use the Orientation settings.
The Thread Profile page color-codes the tree results:
- Red: Percentages greater than 30%
- Yellow: Percentages greater than 10%
- Black: Percentages less than 10%
Here are some additional options for viewing x-ray session's thread profile results.
|If you want to...||Do this...|
|View the associated key transaction or app||Select either link above the thread profiler results.|
|View execution details for any row||Mouse over the thread profiler results.|
|Adjust how much information appears in the tree view||From the Tree settings, select Filter outliers, then select Refresh tree.|
|Change the default parent-child (top down) tree view||From the Tree settings, select the Orientation (top down or bottom up), then select Refresh tree.|
|Include specific locations in the call stacks details||From the Tree settings, select Show line numbers, then select Refresh tree.|
|View details for the parent server||Select the Process link.|
Java agent notes
For Java users, your x-ray session's Thread Profile page includes a CPU burn percentage. The CPU burn metric measures your CPU load across the session.
Only threads in a "runnable state" are included in CPU burn. A "runnable" thread is any thread that is executing or waiting to execute. Threads that are waiting on another activity are not "runnable" (for example, a thread waiting for results from disk read).
Use CPU burn for a rough overview of performance across all profiled threads. You can then examine individual thread profiles and compare them in order to better understand your performance.
Python agent notes
For Python users, your x-ray session's thread profile information appears on a single page. For WSGI environments, if your server uses co-routines (green threads), Python users will not see any thread profiling data in the existing thread profiler or in the Thread Profile page for x-ray sessions.
Ruby agent notes
For Ruby users, your x-ray session's thread profile information appears on a single page. Thread profiling is only available for 1.9.2 or higher, and only recommended on MRI. For more information, see the thread profiler Ruby notes.
For more help
Additional documentation resources include:
- X-ray sessions (overview of New Relic's x-ray sessions feature and comparison to standard event thread profilers)
- Starting, stopping, or deleting an x-ray session (procedures)
- Viewing an x-ray session (menu options for existing x-ray sessions)
- X-ray session Overview page (page and drill-down details for the selected x-ray session's transaction traces)