Error tracking with errors inbox

Errors inbox is a single place to proactively detect, triage, and take action on all the errors before they impact customers. Receive alerts whenever a critical, customer-impacting error arises via your preferred communication channel, like Slack.

Resolve errors faster with errors from across your stack, including all APM, browser (RUM), mobile, and serverless (AWS Lambda) data, displayed on one screen. Errors are grouped to cut down on noise, and collaborating across teams is easy with shared visibility to the same error data.

Why it matters

Errors inbox provides a unified error tracking experience to detect and triage errors:

View and triage issues across applications and services that your team cares about for faster error resolutions.
Proactive notifications with detailed error information in Slack.
Error profiles to show similarities between error events and surface the root cause by analyzing attributes.
Analyze errors in context of the full stack and resolve errors with precision.
Errors for APM, browser, mobile, and AWS Lambda functions are all captured in the same inbox.

Ready to get started? Make sure you have a New Relic account. It's free, forever!

Requirements

Access to log management capabilities is limited by user type. See user type capabilities.

Use errors inbox from entity scoped views

Entity scoped views allow you to view errors for a single APM, browser, mobile, or OpenTelemetry application. Access the errors inbox view for a specific entity by navigating to that entity in the APM, browser, mobile, or OpenTelemetry monitoring view and selecting Errors inbox in the left nav under Triage.

Triage errors for an entity by selecting Errors inbox in the left nav of the explorer.

Set up errors inbox with workloads

To enable errors inbox, follow these steps. Afterwards, errors groups should start to appear in your inbox.

From one.newrelic.com select Errors inbox from the top nav.
If this is your first time accessing errors inbox, select a workload in the top left.
If you have no workloads set up, create a workload before using errors inbox.

Once you select your workload, your inbox should populate with error groups.

one.newrelic.com > More > Errors inbox

Monitor errors

Once you've set up your errors inbox, you can begin proactively monitoring all errors in your stack:

Error groups

Error groups are sets of events that make up a unique error. Error groups are stored long term and contain metrics, activity log, discussions, and basic information about the unique error. Error groups are tied to the entity, so making a change to the state of an error group in one errors inbox will impact all other inboxes that contain that entity.

How error groups work

Error events get grouped into an error group when they share the same fingerprint. As events are ingested by New Relic, we run the events through a set of managed rules that output a fingerprint. Every unique fingerprint has a single error group associated with it.

The New Relic managed rules normalize the error data, identifying and ignoring unique values such as UUIDs, hex values, email addresses, etc. that would cause grouping “like” errors into unique groups. NR account ID, entity ID, error class, error message, stack trace and exception are all data that can impact a fingerprint.

If you see “like” error events grouped into different error groups incorrectly, try removing the unique identifier from the error class or message and store those as attributes instead. This will allow you to more easily facet on the attribute values and reduce the number of error groups.

If you have a single application reporting as multiple entities in New Relic (running in different clusters, cells, etc.), you might see duplicate error groups, since our grouping logic looks at account and entity IDs as part of the fingerprinting process. You can consider rolling up the multiple entities into a single entity and including only that rolled up entity as part of your errors inbox.

You can also use the feedback tool in NR1 to share error groups that could use improved grouping. We’re continually updating our rules to improve the quality of error groups.

Occurrences

Your errors inbox displays the total number of occurrences of each error group within the selected timeframe. The corresponding sparkline chart displays the total number of occurrences per day over the selected timeframe as you hover over it.

Sort By filter

Using the dropdown in the top right, you can sort the list of grouped errors by the number of occurrences or by the error that was last seen (latest first).

Regression tag

An error group is tagged with a regression tag when a new error matches a resolved error group’s fingerprint. The regression tag will disappear once a regressed error group's state is changed.

Bulk actions

You can resolve, ignore, or unresolve errors in bulk with the Edit groups dropdown.

You can update the status of multiple error groups (up to 2,000) all at once. In the inbox view, check the Error groups checkbox to update all of your error groups in the inbox. You can also select individual error groups to update their statuses.

First and last seen dates

We understand it's very useful to know when an error group was first seen in order to correlate it with a change in the code/system. The accuracy of first and last seen dates depends on the three scenarios outlined below:

Scenario 1: If an error group was first created on or after 5/17/2022, first and last seen values are accurate.
Scenario 2: If an error group was first created before 5/17/2022, the first seen date will not be accurate. The first seen date is either 5/17/2022 or the date of the earliest occurrence (if the time window selected is before 5/17/2022). The last seen value will be accurate.
Scenario 3: If an error group occurs once per week or less, the first and last seen dates are estimates based on the time of the single occurrence. We only track first and last seen dates accurately for errors that show up more than once per week.

Triage errors

Errors status

Errors inbox enables you to triage error groups directly from the main screen or from the error details page. Triaging helps remove the noise from your errors inbox, and lets you focus on the high impact errors that need attention.

You can set one of three statuses, and filter your inbox by status.

Unresolved: This is the default status of error groups.
Resolved: Setting an error as resolved will hide it from the default inbox view unless filters are updated to include resolved errors. If events matching the error group fingerprint occur after marking an error group as resolved, it will automatically reset the status to Unresolved. This can be useful for identifying regressions.
Ignored: Ignored will hide the error group from the inbox view unless filters are updated to include ignored errors, or until you stop ignoring the error group.

Error details

Clicking on a specific error group takes you to the error details page, where you will find full context of the issue. This context can assist in triaging the error and assigning it to the correct team or individual.

The Discussions tab provides room for detailed and organized collaboration. This is key to looping in collaborators and ensuring the entire team has the same context regardless of where they sit. Discussions includes:

Threaded conversations: Reply directly to top level comments to tie replies to specific posts.
Comment deletion: Delete comments. The content of the post will be removed unless it is the parent of a thread, in which case the box will remain with the message “Comment deleted by user.”
Markdown support: Add styling and links to your comments in Markdown.

Assign errors

You can assign an error group to anyone. Simply select the user from the assign dropdown menu. You may also assign an error to any email address, even if they aren’t a New Relic user.

You can update the filter in errors inbox to show only errors assigned to yourself, or a teammate.

Why it matters

Requirements

Use errors inbox from entity scoped views

Set up errors inbox with workloads

Monitor errors

Error groups

Troubleshooting: similar looking events do not group together

Occurrences

Sort By filter

Regression tag

Bulk actions

First and last seen dates

Triage errors

Errors status

Error details

Occurrences

Attributes

Activity

Discussions

Assign errors