Transactions page: Find specific performance problems

New Relic APM's Transactions page helps you identify transactions that may be good candidates for fine-tuning performance problems or resolving errors. This page lists the selected app's transaction Requests, the top five transactions by percent of wall clock time, and relevant throughputs (requests per minute or rpm). For non-web transactions (such as message processing, background tasks, and other processes and jobs that do not handle web requests), this page shows charts of CPU and memory usage.

Access to this feature depends on your subscription level.

Wall clock time

Wall clock time is the amount of time recorded by the clock. New Relic uses wall clock time for all the transactions and then sums that value across all of the transactions.

The host can execute requests in parallel, so you may see percentages over 100. For example, 100% would indicate that the execution time across all selected transactions is equal to the time expended when recording wall clock time.

Types of transactions

Depending on your selected application, the Transactions page may include a dropdown you can use to select from the types of transactions available. New Relic measures processing time by type of request (web or non-web). This may include:

  • Web: App server requests
  • Non-web: Other requests (operations, background tasks, etc.)

The Transactions page also may include links to transaction traces and key transactions. The types of information available will depend on your selected app, the type of request (web or non-web), and your New Relic subscription level.

View transactions

To quickly see the details of one of your app's top five transactions: Go to rpm.newrelic.com/apm > (select an app) > Monitoring > Overview, then select a Transaction link from the APM Overview page.

To view information about your app's transaction requests:

  1. Go to rpm.newrelic.com/apm > (select an app) > Monitoring > Transactions.
  2. If applicable: To change which available types of transactions appear, select the Type.
  3. Select the sort order, or keep the default.
  4. Select the type of view as a chart (default), histogram, or percentile, if available.
  5. To view additional details, use any of the transaction drill-down functions.
  6. To add a chart to New Relic Insights, mouse over the chart, then select the Add to an Insights dashboard link that appears below it.

If a chart's background is light red, this indicates a time period when an alert condition's Critical threshold has been violated. To view the incident details in New Relic Alerts, click the chart.

New Relic APM: Transactions page
rpm.newrelic.com > (select an app) > Monitoring > Transactions: Use the Transactions page to examine the top transactions that may indicate areas to fine-tune performance, or drill down deeper into individual transactions and trace details. Here is an example of an app with an alert violation in progress. (The chart's background is light red.)

Use drill-down functions

Use any of New Relic's standard user interface functions to drill down into detailed information. The Transactions page has additional drill-down functions.

Change the displayed transaction Type

APM Transactions type

If the Type dropdown appears above list of transactions, you can select your choice of transaction type. The available types depend on what transactions your application uses.

Select the type of performance measurement (Sort)

Sort option - Most time consuming

The Sort dropdown above the transaction list allows you to review transactions according to different measurements. This helps you identify good candidates for performance tuning or fixing errors.

You can sort by:

Sort option Comments
Most time consuming (default)

Highest percentage of the app's total time used.

This measures which transactions consumed the most time in total. This is calculated by multiplying the number of times the transaction by the time the transaction took to complete. A transaction could be short, but if it is frequently called, it would appear at the top of this ranking.

Slowest average response time

Slowest individual transactions for the time period as averaged.

This measures the slowest types of transaction. A transaction could be called only a few times, but if it is one of the longest transactions to finish, it would appear at the top of this ranking.

Apdex most dissatisfying

Transactions with the highest percentages of user dissatisfaction levels for the response time of your web apps and services (Apdex).

The dissatisfaction level is the difference between a perfect Apdex score (1.0) and your app's apdex_t ("tolerating") score, based on your Apdex settings. Transactions that have the highest (worst) percentages appear at the top of this ranking.

Highest throughput

This measures the amount of throughput, in operation requests per minute or rpm. (For web throughput, requests per minute is sometimes called pages per minute or ppm.) Transactions that have the highest number of requests per minute appear at the top of this ranking.

Depending on the transaction type you choose, different sort options may be available.

Mouse over summary information about a transaction

crop-tx-summary-details

To quickly view key pieces of information about the transaction, mouse over its name on the list.

Select detailed information about a transaction

Transaction details tab

To view detailed information, select a transaction from the list, then select App performance or Historical performance. You can also view transaction traces.

View transaction data in different visual formats

Select chart options

The Transaction page's Top 5 transactions chart and a selected transaction's App performance window include options to view data as a:

In addition, from the Breakdown table for a selected transaction, you can select the link to show or hide all segments of the breakdown data.

Show corresponding Browser request data

In order to view browser information, you must enable New Relic Browser. Then, to view corresponding browser request data, use either of these options:

Identify transaction segments with high call counts or time

Transaction segment with high call time count colorization

In a transaction's Breakdown table, the Avg calls (per txn) column may include colorized segment values. These indicate instrumented segments that have exceeded thresholds.

  • yellow square Yellow: Segment time is more than 10% of total transaction time and call count is higher than 10.
  • red square Red: Segment time is more than 10% of total transaction time and call count is higher than 20.

Show all transactions

To view all available transactions as a table, select the Show all transactions table link. From here, use any of the available options:

  • To change the sort order, select any column header.
  • To export the data to a file with comma-separated values, select Export as CSV.
  • To return to the previous chart view, select Back to top transactions.

CSV tables for ending now time periods are calculated at run time. They may show slightly higher values than what appears in the APM table.

For each transaction, the Show all transactions table includes these measurements:

Measurement Definition
Apdex

The average Apdex score for all transactions that occurred in the selected time range.

Apdex scores marked with an * asterisk indicate the agent collected fewer than 100 samples for that transaction name. Data for these transactions may be less accurate than data for transactions with higher throughput.

Count The total number of all transactions that occurred in the selected time range.
Avg (ms) The average time taken by all transactions in the selected time range.
SD (ms) The standard deviation of all timing measurements for all transactions in the selected time range.
Min (ms) The time taken by the fastest transaction in the selected time range.
Max (ms) The time taken by the slowest transaction in the selected time range.
Total (ms) The total amount of time taken by all transactions that occurred in the selected time range.
Total (% time) The total amount of time for all transactions of that type, expressed as a percentage of the total amount of time taken by all transactions.
Dissat (%)

The percentage of the transactions that did not have satisfied Apdex scores.

If you view transactions as a table, the All transactions row always contributes 100% of the app's total dissatisfaction, even if no responses are dissatisfying (100% of zero is zero). In this situation, 100% does not mean that all of your transactions are dissatisfying. The sum of all the other values in the Dissat (%) column is 100%.

Additional subscription-level functions

Depending on your subscription level, additional functions may be available for the Transactions page's selected transaction.

If you want to... Do this...
View transactions for operations and other background tasks

Change the Type to Other transactions (or a specific type listed), then select a specific transaction.

The Transactions page shows the top five transactions for this selection by wall clock time, CPU usage, and memory usage.

Track a transaction that is important to your business Select the transaction's name, then select Track as key transaction.
View transaction trace details

A transaction trace is a complete picture of a single transaction.

  1. From the Transactions page, select the transaction trace.
  2. Select the view for Summary, Trace details, or Database queries, if available.
  3. To expand the transaction trace to full screen view, select the full screen [expand icon] icon.
  4. To return to the Transactions page: Next to the transaction trace's name, select the back arrow.
Delete all transaction traces

If you select Delete all traces, you cannot recover them.

Depending on your subscription level and data retention policy, you can also use the Web transactions analysis report for web transactions and the Background jobs analysis report for non-web transactions to compare the amount of time spent in throughput, total time in the transaction, average time to execute it, and Apdex score as applicable.

For more help

Recommendations for learning more: