Viewing APM errors and error traces (legacy)

Legacy

On December 1, 2015, we released our new Errors page in APM for customers using the most recent agent versions for Java, Node.js, PHP, Python, and Ruby. This document is for the old Errors page. The old Errors 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

 

[video link] To learn about using transaction traces and traced errors to troubleshoot your app, watch this video (approximately 16 minutes).

Viewing the Errors page

screen-errors-dashboard.png
APM > (selected app) > Events > Errors: Here is an example of the Errors page and message details for the selected error.

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.

Label Explanation
Time The time at which the error occurred.
Instance

The instance of the application on which the error was reported. Format:

Server name (application name)

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 COUNT is the total number of times this error occurred during the time range indicated. The arrows allow you change the time range.
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:

  1. From the New Relic menu bar, select APM > Applications > (selected app) > Events > Errors > (selected error message).
  2. Select Delete this error.
Delete all error traces for your app

Owner or Admins

To delete all error traces for the selected app:

  1. From the New Relic menu bar, select APM > Applications > (selected app) > Events > Errors.
  2. Select Delete all errors.
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)

Join the discussion about New Relic APM in the New Relic Online Technical Community! The Technical Community is a public platform to discuss and troubleshoot your New Relic toolset.

If you need additional help, get support at support.newrelic.com.