To view transaction trace data, go to one.newrelic.com APM & services > (select an app) > Monitor > Transactions > (select a transaction trace). The transaction trace's Summary page has four main areas:
Primary trace data, functions
At the top of all transaction trace pages are some primary measurements and functions. Measurements include response time, trace time, and, if available, CPU info. Sometimes there also may be a note that it is a partial trace.
Available functions include:
This chart shows the trace segments that took the longest time, ordered by percentage of time spent. The remaining trace segments are grouped as Remainder.
To show additional display options, mouse over the chart.
The Slowest components table shows the number of calls, total duration, and percentage for each of the slowest components.
This section displays available transaction attributes, including default attributes (such as referring URL and request headers) and custom attributes. The exact request attributes collected by default depend on the New Relic language agent you use.
To turn attribute collection on or off for traces, you can either use the agent config file or the UI Settings > Application page (if your New Relic agent allows server-side configuration).
The other main transaction trace UI page is the Trace details page.
You can also bring your logs and application's data together to make troubleshooting easier and faster. With logs in context, you can see log messages related to your errors and traces directly in your app's UI. You can also see logs in context of your infrastructure data, such as Kubernetes clusters. No need to switch to another UI page.