New Relic APM's Transactions 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), the page shows charts of CPU and memory usage.
For web throughput, requests per minute (or rpm) is sometimes called pages per minute (or ppm).
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 server 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 from which you can select from the types of transactions available. 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 subscription level.
To view information about your app's transaction requests:
- From the New Relic menu bar, select APM > (selected app) > Monitoring > Transactions.
- If applicable: To change which available types of transactions appear, select the Type.
- Select the sort order or keep the default.
- Select the type of view as a chart (default), histogram, or percentile, if available.
- Use any of the transaction drill-down functions to view additional details.
To go directly to the Transactions page for one of your app's top five transactions: From the New Relic menu bar, select APM > (selected app) > Monitoring > Overview, then select a Transaction link from the APM Overview page.
Use drill-down functions
|If you want to...||Do this...|
|Change the displayed transaction Type||
If the Type dropdown appears above list of transactions, you can select your choice of transaction type. Types available depend on what transactions your application uses.
The Sort dropdown is above the transaction list. The default Sort option is Most time consuming. Other possible Sort options include: Slowest average response time, Apdex most dissatisfying, and Highest throughput. Depending on the transaction type chosen, different sort options may be available.
|View summary transaction info||
Mouse over a transaction's name on the list to see a few important pieces of information.
|View details about a transaction||
Select a transaction from the list. You can then select App performance or Historical performance for that transaction.
For information about transaction traces, see Viewing transaction traces.
|View transaction data in different visual formats||
From the Breakdown table for a selected transaction, you can also select the link to show, or hide, all segments of the breakdown data.
|View corresponding browser request data||
Select the Browser drill-down link if available or, from the New Relic menu bar, select Browser > (selected app) > Page views.
In order to view browser information, you must enable page load timing (sometimes referred to as real user monitoring or RUM).
|Identify transaction segments with high call/time count||
In a transaction's Breakdown table, there is a column for Avg calls (per txn). External and datastore transaction segment numbers here may show up yellow or red:
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.
Apdex scores marked with an
* asterisk indicate the agent collected less than 100 samples for that transaction name. Data for these transactions may be less accurate than data for transactions with higher throughput.
Here are definitions for the measurements in the Show all transactions table:
|Apdex||The average Apdex score for all transactions that occurred in the selected time range.|
|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.|
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||
To expand the transaction trace to full screen view, select the fullscreen [expand] icon.
To return to the Transactions page, select the back arrow next to the transaction trace's name.
|Delete all transaction traces||
If you select Delete all traces, you cannot recover them. For more information, see Deleting transaction traces.
For more help
Additional documentation resources include:
- Web transactions analysis report for web transactions and Background jobs analysis report for non-web transactions (how to use the reports available in the UI to compare the amount of time spent in throughput (requests per minute or rpm), total time in the transaction, average time to execute it, and Apdex score as applicable)
- Viewing transaction traces (how to interpret transaction trace data)
- Request queueing and tracking front-end time (how APM measures processing time)
- Monitoring background processes (how to set up background monitoring for your agent and view the processes from the Transactions page in the UI)