Introduction to transaction traces

In New Relic APM, a transaction trace gives a detailed snapshot of a single transaction in your application. A transaction trace records the available function calls, database calls, and external calls. You can use transaction traces to troubleshoot performance issues and to get detailed low-level insight into how your app is working.

Access to this feature depends on your subscription level.

What transactions record traces

In New Relic APM, a transaction trace records the segments that make up a transaction. Because they give you more detail, you can use transaction traces to analyze and troubleshoot performance issues.

To see how all your applications, services, containers, cloud services, hosts, and other entities work together, use New Relic One.

Here are the default rules that govern which transactions a New Relic agent traces:

  • Over the minute-long harvest cycle, all transactions that violate the threshold (either four times your Apdex T value or a specific number of seconds) are added to a pool of transactions.
  • At the end of that minute, the New Relic agent selects the slowest transaction in that pool and performs a transaction trace on it.

These are the general rules, but there are some agent-specific differences. For example:

  • The Java agent collects occasional non-slow transactions.
  • If one transaction is frequently traced, some agents will select other transactions to give a more diverse sampling.

If you don't see traces in your account, it's possible that no transactions meet the necessary criteria. In this situation, you can adjust transaction trace settings to ensure some transactions will be traced.

If you use New Relic Synthetics, you will likely have Synthetics monitor traces. Synthetics traces can happen more frequently than APM traces, potentially several per minute.

Configure transaction traces

To configure or edit trace settings, see the procedures for:

View transaction traces in UI

APM - Transaction trace page

rpm.newrelic.com/apm > (select an app) > Transactions > (select a transaction trace): This is the transaction trace summary page in New Relic APM. You can also view in-depth details in the Trace details page and examine database queries, if present, in the Database queries page.

To view transaction traces in the New Relic UI:

In New Relic One
  • Go to one.newrelic.com > Entity explorer > (select an app), then click the Throughput table's title for your selected app, and select a trace from the Transactions page.

    OR

  • Go to one.newrelic.com > Entity explorer > (select an app) > Explore performance > Transactions, and select a trace from the Transactions page.

For more information, see the documentation about navigating core UI components in New Relic One.

In New Relic APM Transactions page
  1. Go to rpm.newrelic.com/apm > (select an app) > Transactions.
  2. Under Transaction traces, select a transaction trace to view its Summary page.
In New Relic APM Overview page
  1. Go to rpm.newrelic.com/apm > (select an app) > Overview.
  2. From the Transactions chart on the selected app's Overview page, select a transaction's trace link.

Once you select a transaction trace, you can view additional details:

Troubleshoot an issue with transaction traces

If you expect to see transaction traces but do not see them, follow the troubleshooting procedures.

To watch a video about using transaction traces and traced errors to troubleshoot your app, visit learn.newrelic.com. For more information about using transaction traces, slow queries, and service maps to solve performance issues, see Analyze performance issues.

For more help

Recommendations for learning more: