On December 1, 2015, New Relic released a new Error analytics page in APM for customers using the most recent agent versions for Java, Node.js, PHP, Python, and Ruby. This document is for the legacy Errors page. This page will be retired in favor of the Error analytics experience in the future.
New Relic APM's Errors page shows a chart with the error rate percentage for the selected time period. It also shows a list of error messages. You can view and drill down details, use search and sort options, hide or delete the error, share it with others, or file a ticket about it.
The Errors chart also appears on the selected app's Overview page. If the chart shows errors, you can select its Error rate title to go directly to this Errors page.
Using the Errors page
Viewing the Errors page
To view, use search options, or delete errors: From the New Relic menu bar, select APM > (selected app) > Events > Errors. Use any of New Relic's standard user interface functions and page functions to drill down into detailed information.
Selecting error details
To view details about an error message on the Errors page, select its Message link. From here you can:
- Share the error message with others by email.
- File a ticket about it (for example, Lighthouse, Pivotal Tracker, JIRA).
- Delete or hide the error.
- Return to the Errors page.
Tip: If you are doing general record cleanup, you may also want to delete transaction traces or database queries. This will remove potentially sensitive data while retaining your other application data (such as Apdex, deployment information, etc.).
Because the New Relic agents collect only a sample of error messages, the number of error messages listed may not equal the total error count indicated in the tooltip shown when you mouse over the Error rate chart.
Error trace details
Here is a summary of the data available in the Error trace detail page. The labels on the example page are used to identify the data available.
|Time||The time at which the error occurred.|
The instance of the application on which the error was reported. Format:
|Count||The number of times this error message was encountered during the selected time range.|
|Similar errors to this||The number shown here plus the
|Error message||The text of the error message selected. It is reproduced at the top of the trace detail page.|
|Sample stack trace||The trace back resulting from the error.|
Disabling error traces
If there are errors you do not want reporting to New Relic, disable them in the configuration file for your agent. For most agents, you can ignore certain error codes or disable errors completely. For more information, see your specific agent configuration documentation:
Delete error traces
You cannot recover error traces after you delete them.
|If you want to...||Do this...|
|Delete individual error traces||
To delete an individual error trace:
|Delete all error traces for your app||
Owner or Admins
To delete all error traces for the selected app:
|Delete all error traces for your account||To delete all error traces for your New Relic account, get support at support.newrelic.com.|
In addition to deleting error traces, you may also want to delete transaction traces or database queries. This will remove potentially sensitive data while retaining your other application data (such as Apdex, deployment information, etc.).
For more help
Additional documentation resources include:
- Collecting custom attributes (capturing and viewing standard HTTP attributes, as well as custom attributes, with every transaction trace, browser trace, and error record)
- Ticketing integrations (how to create Atlassian JIRA issues, Lighthouse tickets, or Pivotal Tracker stories from transaction traces, errors, and notes in New Relic)