APM Summary page: View transaction, Apdex, usage data
The APM Summary page provides general information about the selected app, including web transactions and non-web transactions, Apdex score, CPU usage, throughput (requests per minute or rpm), transaction times, error rate, application activity, and hosts.
To get a high-level overview of all your applications and services, use the New Relic explorer.
View your app's summary page
To reach the Summary page, go to one.newrelic.com > APM & Services > (select an app). Use All entities to access all your entities, that is, anything we can identify that reports data, from applications and hosts to custom groupings of any elements.
As of June 30, 2022, we're discontinuing support for several capabilities, including the classic APM Summary page that you could toggle on and off in the UI. For more details, including how you can easily prepare for this transition, see our Support Forum post.
View app performance
Use the Summary page for a quick summary of your website's performance.
Some charts include links to APM pages where you can drill down into additional details.
Also, for your external or background services, you may see data labeled as Web external. For more information about these out-of-process services, use the Externals page.
This chart measures the performance of your app based on its Apdex T value during the selected time window. To view additional details, hover over the question
icon or the chart's End user and App server lines. The End user line charts the Apdex for your browser apps, and the App server line charts the Apdex for your APM apps.
This chart illustrates the requests per minute for either web transactions or non-web transactions. To change the type of transaction, select the Transaction response time chart's dropdown arrow, then select Web or Non-web.
This chart shows the number of errors that have occurred in the current time window. The tooltip that appears when you hover over the Error rate chart shows the combined throughput for both web and non-web transactions. To understand how error rate is calculated, see Application error rate example.
Markers on the main Summary chart indicate events and changes to the app:
Black vertical bar: Apdex settings have changed.
Blue vertical bar: A deployment marker has been created or another event has occurred, such as a settings change for the app.
Yellow or red area: This indicates alert thresholds have been violated.
To view additional information, mouse over the marker.
Use any of New Relic's standard page functions to drill down into detailed information. Here is a summary of additional options with the APM Summary page.
Mouse over the Apdex score ? icon. For non-web transactions, the Apdex chart is blank because Apdex is not applicable to this class of apps.
View trends in transaction time, Apdex, and throughput
Select the Compare with yesterday and last week checkbox.
The checkbox is only available when viewing the Web transaction response time chart with the time picker window Ending now. The checkbox is unavailable if you are viewing histograms, percentiles, or custom dates.
View app performance since the last deployment
From the time picker, select Performance since the last deployment. For detailed information about all deployments, select the Deployments page.
Select the Error rate chart's title on the APM Summary page. You can also view the Errors page from one.newrelic.com > (select an app) > Events > Errors. From here you can also view available error logs in context for your app.
Once the browser agent is set up, the APM Summary page provides summary information and direct links to detailed information on the app's corresponding browser summary page.
To view chart details with browser page load time, select the main chart's Browser link.
To view the Apdex score for browsers, select the Apdex chart's Browser link.
Link app performance to resources
The APM Summary page shows a table with averages about your app's instances on their hosts, including:
CPU usage percentage is calculated as though the application is running on one CPU core. For more information about this calculation, see CPU usage is over 100%.
Use any of these options to examine your app's performance within the context of your system's architecture and resources, such as individual hosts:
Select your choice from the table at the bottom of the APM Summary page for infrastructure.
Toggle between a table view or breakout metric details.
If applicable, select your choice from the drop-down at the top of the APM Summary page for servers or JVMs.
To help you understand the full context of your app's performance within your environment, APM includes options to view performance from inside the application, as well as from outside the application with the infrastructure agent.
To view detailed information from your resources' point of view, click any host link. The link takes you directly to the infrastructure Compute page.
When you click, the Compute data may not immediately appear. If that happens, follow the prompt to validate your account and complete the conversion process for the infrastructure agent. If you need additional help, get support at support.newrelic.com.
To troubleshoot the host link from the APM Summary page, use these tips:
Host link from APM Summary
Your infrastructure agent is not installed on the host.
The application is operating within a container, and your infrastructure agent is installed on the container’s host.
Set the hostname for the container to be the hostname of the underlying server.
Docker containers: Run your Docker container with the argument:
This will cause the container to share the UTS Linux Namespace with the underlying host. However, by using this set, a privileged container could change the host's hostname.
The application is running on a Windows container, and your infrastructure agent is installed on the Windows host.
To get a direct link to infrastructure metric data for your application, enable process metrics in the infrastructure agent's configuration.
Your infrastructure agent is installed, but it only reports the short hostname, not the long hostname.
Configure your server's hostname settings so that the infrastructure agent and the APM agent return the exact same name string. If possible, do so by editing your server's fully qualified domain name (FQDN) settings.
The APM and infrastructure agents both read their hostname from the operating system's FQDN settings, so setting the hostname there ensures both agents share a single hostname. For more information, see the Java agent troubleshooting example.