New Relic APM's Error analytics page includes detailed information about error traces. By default, the Error traces table shows the most recent error traces, grouped by transaction name and error class. You can also filter traces, change the sort order, and drill down into more detailed error information for a selected trace, including:
- Stack trace details
- Framework code underlying the stack trace
- Default attributes and custom attributes from New Relic Insights that relate to the specific occurrence of the error
- The related transaction (via the link to New Relic APM's Transactions page)
If you have integrated your ticketing system with New Relic, you can also view related tickets or stories, or file a new ticket or story with JIRA, Lighthouse, or Pivotal Tracker.
Access to this feature depends on your subscription level.
Contents
View error trace details
To examine and act on details about an error trace from New Relic APM's Error analytics page:
- From rpm.newrelic.com, select APM > Applications > (selected app) > Events > Error analytics.
- From the Error traces table, review the list of error traces for the selected time period.
- To change the sort order, select any column header.
- To view details about a specific trace, including stack trace and framework code, host, timestamp, URL, and default attributes or custom attributes from New Relic Insights: From the Error traces table, select the transaction name.
- To view related transaction details: Below the trace detail's error trace name, select the transaction name.
- To share the error trace details, select the ticketing integration link for Lighthouse, Pivotal Tracker, or JIRA.
- To view any Lighthouse or JIRA tickets or Pivotal Tracker stories already filed, select Related tickets.
- To return to the Error analytics page, select Errors.
If the error category does not have any associated trace detail during the time period, the category will appear gray, and you cannot select it. Try removing some error filters or expanding your time window.
Disable error traces
To prevent certain errors from being reported to New Relic, disable them in your agent's configuration file. For most agents, you can ignore certain error codes or disable errors completely. For more information, see your specific agent's configuration documentation:
- Go (not applicable; the agent only reports errors when configured to do so)
- Java
- .NET
- Node.js
- PHP
- Python
- Ruby
Delete error traces
You cannot recover error traces after you delete them.
| If you want to... | Do this... |
|---|---|
| Delete all error traces for your app |
To delete all error traces for an app:
|
| Delete all error traces for your account | To delete all error traces for your New Relic account, get support at support.newrelic.com. |
| Delete individual error traces | To delete individual error traces, use New Relic APM's Errors page. |
In addition to deleting error traces, you may also want to delete transaction traces or database/slow SQL traces. 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:
- Error analytics: Compatibility and requirements (requirements to use New Relic's error analytics feature, including events or metrics views, agent versions, data retention, and caps on error reporting)
- Error analytics: Explore the events behind the errors (detailed investigation of app errors, including summary data you can filter and group, top errors that may be related to alerts or custom Insights events, trace details, and patterns in frequency over time)
- Error event default attributes for Insights (a listing of the attributes captured for error events)
- Collecting custom attributes (capturing and viewing standard HTTP attributes, as well as custom attributes, with every transaction trace, browser trace, and error record)