The Issues page displays information about errors in your application. Filter by properties such as browser, device, impacted users, or whether the error is unhandled. You can then inspect issue details to better understand the problem and triage effectively.

Issues homepage

A typical application sends a large number of events to Sentry. You can think of an issue as a single bug or problem with your app. To make them manageable, we group similar events into issues based on the event stack trace and other information. This grouping of events into issues allows you to see how frequently a problem is happening and how many users it's affecting.

For each issue, the page displays:

  • Error type and message
  • Brief description of the issue
  • Associated project
  • Issue timing, such as last and first time seen

You can also hover over the issue title to see the stack trace of the latest event.

When you click on an issue on the main Issues page, the Issue Details page displays.

From the Issues page, you can begin to triage. The page is organized into tabs, each corresponding to a filtered list of issues, and these different lists help you with triaging:

  • All Unresolved (is:unresolved): All unresolved issues, including issues that need review.
  • For Review (is:unresolved is:for_review): Also called Review List. Issues that need to be reviewed; for-review issues are a sub-set of all unresolved issues.
  • Ignored (is:ignored): All ignored issues.
  • Saved Searches: Select from a set of recommended and custom saved searches. The name of the tab changes based on your selection.

Learn more about triaging issues and their different states in Issue States and Triage.

If you're an Early Adopter, you can also add issues data to your custom dashboards, as widgets, using the data set selector.

Learn More

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