Transaction traces

Note: The Transaction Tracing feature is for New Relic Pro subscriptions and higher.

Transaction tracing extends the New Relic service to the tiniest transaction detail levels. Primarily, New Relic only collects streaming metric data. This data is aggregated, so that if the ORM Layer (such as ActiveRecord or Hibernate) was invoked 100 times during a 60 second time period, New Relic would collect one metric that was an aggregate of the 100 invocations.

With the Transaction Tracing feature, just the opposite is true. Each minute transaction tracers collect data for your slowest individual HTTP requests, all the way down to the SQL. If a transaction takes longer than a configurable time period, New Relic captures the exact invocation pattern and details related to the invocation, such as the exact SQL statement that was issued.

Getting started

Video For an overview of how to use New Relic's Transaction Traces features, watch this video (less than 6 minutes).

To set up the Transaction Traces features: From the New Relic menu bar, select Applications > (selected app) > Settings > Application. For more information, see Configuring transaction traces.

To view transaction trace records, do either of the following:

  • From the New Relic menu bar, select Applications > (selected app) > Monitoring > Overview, and then select the Requests view. Then, from the Applications Overview dashboard's Transactions section, select a link for any app server trace.
  • OR: From the New Relic menu bar, select Applications > (selected app) > Monitoring > Transactions, and from the Transactions dashboard, select a link for any app server transaction trace.

For more information, see Viewing transaction traces.

Transaction Trace
Applications > (selected app) > Transactions > (selected transaction trace): Here is an example of the information captured by a transaction trace.


The transaction trace's Summary shows each segment of the trace as colored bars. Red does not necessarily mean there is a problem; it simply indicates that a significant amount of time was spent in that segment. You will need to determine a "normal" or "typical" value for the process in order to evaluate whether a red area on the bar chart actually indicates a problem.

For more help

Additional documentation resources include:

If you need additional help, get support at