New Relic APM's Overview 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, recent events, and hosts.
To get a high-level overview of all your applications and services, use the entity explorer in New Relic One.
View your app's Overview page
To get started:
- In New Relic One
Go to one.newrelic.com > Entity explorer > (select an app), then click the Web (or Non-web) transaction breakdown table's title for your selected app.
Go to one.newrelic.com > Entity explorer > (select an app) > Explore performance > Overview.
For more information, see the documentation about navigating core UI components in New Relic One.
- In New Relic APM
Go to rpm.newrelic.com/apm > (select an app). Your app's Overview page automatically appears.
- To select an app from your account's Applications index, select the Applications link.
- To search for or filter your list of apps, select the Apps dropdown.
View app performance
Use the Overview page for a quick summary of your website's performance.
- Overview charts
Some charts include links to New Relic APM pages where you can drill down into additional details.
APM Overview chart Comments Transactions response time
This stacked chart represents the response time of web transactions or non-web transactions in your app. Segments in the chart vary depending on which agent you are using. Some charts may have an independent line for response time that represents the relationship between response time and total time.
Apdex score 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 question circle 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. Throughput 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. Error rate 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.
- Event markers
Markers on the main Overview 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.
- Drill-down details
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 Overview page.
If you want to... Do this... Change how data appears on the main chart Select the chart title's drop-down arrow, and then select your choice of view options, including histograms or percentiles if available. View threshold levels for your app's Apdex score 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 View the Transactions page Select the Transactions table's heading on the APM Overview page. Or, to view details about a specific transaction (including operations, transaction traces, and key transactions), select its name. View the Databases or External services pages Click on a related time band in the Web transactions response time chart. View the Errors page
Select the Error rate chart's title on the APM Overview page. You can also view the Errors page from rpm.newrelic.com/apm > (select an app) > Events > Errors.
- Browser details
In order to view Browser details, you must enable this feature from Browser settings. However, if your app has never reported any browser monitoring data, you must first enable it from the application's settings:
- Go to rpm.newrelic.com/apm > (select an app) > Settings > Application.
- From the New Relic Browser section, select the Enable browser monitoring? checkbox.
- Select Apdex values for browser monitoring and app server requests, or leave the defaults.
- Optional: Select up to five countries or regions for browser monitoring to highlight on the Geography page.
- Select Save application settings.
- To enable additional features, follow standard procedures from Browser > (selected app) > Settings.
After New Relic Browser instrumentation is set up, the APM Overview page provides summary information and direct links to detailed information on the app's corresponding Browser Overview 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 Overview page shows a table with averages about your app's instances on their hosts, including:
- Response time
- Error rate
- CPU usage
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%.
- Examine app performance within system context
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 Overview page for New Relic 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 Overview page for servers or JVMs.
- Examine details within New Relic Infrastructure
To help you understand the full context of your app's performance within your environment, New Relic APM includes options to view performance from inside the application, as well as from outside the application with the New Relic Infrastructure agent.
To view detailed information from your resources' point of view, click any host link. The link takes you directly to New Relic Infrastructure's 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 New Relic Infrastructure. If you need additional help, get support at support.newrelic.com.
To troubleshoot the host link from the APM Overview page, use these tips:
Host link from APM Overview Troubleshooting tips Your New Relic Infrastructure agent is not installed on the host.
Follow standard procedures to install New Relic Infrastructure.
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.
Your New Relic Infrastructure agent is installed, but it only reports the short hostname, not the long hostname.
Configure your server's hostname settings so that Infrastructure 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.