Error Issues

Learn how to use the information on the Issue Details page to debug an error issue.

An error issue is a grouping of error events. What counts as an error varies by platform, but in general, if there's something that looks like an exception, it can be captured as an error in Sentry. Sentry automatically captures errors, uncaught exceptions, and unhandled rejections, as well as other types of errors, depending on platform. We group similar error events into issues based on a fingerprint. For error issues, a fingerprint is primarily defined by the event stack trace.

Issue details

To subscribe to an error issue and receive alerts about it, click the bell icon, then fine tune workflow notifications related to the issue in User Settings > Notifications.

The event description is displayed just below the issue title along with an icon representing the error level of the event:

Error level icon in issue details

The level can be:

  • Error - orange
  • Info - blue
  • Warning - yellow
  • Fatal - red
  • Debug - gray
  • Sample - purple

In the right hand sidebar, reflects a summary that includes information such as how often the error issue has occurred in the last 24 hours and the last 30 days, as well as the last time and the first time the issue was seen. If the issue is linked to any GitHub or Jira issues, that's displayed here as well. You can also use this section to link to existing GitHub or Jira issues. Learn more about linking issues in Integrations. Lastly, there is a facet map, which shows the distribution of values for the tags for all events included in the error issue. All of these values are based on the environment that you've selected in the environment dropdown.

Event Grouping

The "Event Grouping Information" section provides details of how Sentry fingerprinted the event into the group. You can see which parts of the stack trace contributed to the fingerprint as well as all values that were available. You can also use the "Grouping Config" dropdown to experiment with other grouping algorithms.

Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").