Use APM's Errors UI in New Relic One to:
- Investigate error information by grouping and filtering the data.
- Add new errors to APM, prevent certain errors from being reported, and configure expected errors.
- Get alerts about errors.
- Review stack traces, logs, and other details.
- Share the error information with charts and dashboards.
View the APM Errors page
To view the Errors UI page:
Go to one.newrelic.com > APM > (select an app), then click the Error rate table's title on your selected app's Summary page.
Go to one.newrelic.com > APM > (select an app) > Events > Errors.
Caps on error reporting
New Relic caps error reporting at 100 events per minute per agent instance. This prevents error reporting from negatively impacting application performance.
- App running across five hosts: New Relic caps error reporting at 100 events per minute x 5 instances = 500 events per minute.
- App running on one host with ten instances: New Relic caps error reporting at 100 events per minute x 10 instances = 1000 events per minute.
Select the time period for error data
You may notice slight differences in count if your time window is set to ending now. This occurs because the counts for the list and table may be requested at slightly different times as the page auto-refreshes.
Use the error events view workflow
Here is a basic workflow describing how to get the most out of the information you see from the Errors page.
- Start with the Error rate chart to see at a glance whether there are any unexpected spikes, dips, or patterns with errors in general.
- Correlate any general patterns on the Top 5 errors chart to alerts occurring during the same time period. Use the groups and filters to examine the error events and attributes in more detail, and look for patterns with error messages or transaction names.
- Explore and share Error trace table information, including specific stack trace details and logs: associated host, user, framework code, custom attributes, etc.
- Also review the Error profiles page to get visual details about significant differences in the frequency of different values for the events.
- Error rate chart: See patterns immediately
Start with the Error rate chart to see at a glance whether there are any unexpected spikes, dips, or patterns with errors in general. For example, are there any spikes near a recent deployment? You may want to change the selected time period to look for other historical patterns.
This chart always shows the overall error rate and count for the selected time period, even when you filter the rest of the page. If you want to focus your investigation on a particular type of error, use the Top 5 errors chart or the Error traces table.
- Top five errors: Correlate to alerts or Insights events
Use the Top 5 errors chart to identify what error types and how many of those errors occurred during the same time period as the Error rate chart. For example:
- Is the error spike related to a specific class?
- Do the top errors point to a new host that recently got moved into production?
- Are the top error messages repeatedly about failed connections by hosts that you know are in a specific region of your organization?
- Have the chart backgrounds changed color to indicate an alert condition? (Light pink indicates the alert condition's Warning threshold, and dark pink indicates the Critical threshold.)
If you want to... Do this... Change the "top 5" selection By default, Top 5 errors chart shows the top five errors by class. To filter or group by other attributes, such as error message, host, or transaction name, or to select any of your custom attributes, use the search window, or select Back to groupings list. Explore or share the error data The Top 5 errors chart uses error event default attributes along with any custom attributes you have added to this event type. To examine the Top 5 errors data in more detail, or to share it with others, select the View query or View in Insights links that appear when you hover below the chart.
- Error traces: Dive deeper into stack traces, framework code, and more
Supplementing the two charts, the Error traces table groups errors by the transaction name and error class, and links them to relevant error traces.
Each row helps you find answers to questions such as:
- How many of this transaction/class occurred within the selected time period?
- What is the most recent error message?
- When did it first and last occur?
Sometimes it may be more useful to examine error trace data from lowest to highest. For example:
- Which error has the fewest number of occurrences?
- When did a particular error stop (Last occurrence)?
You can change the sort order or filter options to focus on just the types of errors that matter the most to you and your teams. In addition, from the Error traces table, you can drill down into the stack trace and framework code, explore the related transaction, file a ticket, and more.