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.
Here are some tips to get started with New Relic's Transaction Traces feature.
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.
Additional documentation resources include:
If you still have problems, submit a support ticket (for fastest service) or email support @ New Relic. Also, you may be able to find support from the community at Stack Overflow. Tag your post with