With Sentry’s Issues page, you can see information about errors, performance, crons, and replay issues right in your application. Learn more about how to get started here.

The Issues page in Sentry displays information about problems in your application. This page allows you to filter by properties such as browser, device, impacted users, or whether an 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 a fingerprint. This grouping of events into issues allows you to see how frequently a problem is happening and how many users it's affecting.

Issues and Event Quotas

Your quota is consumed by events, not issues. Issues are generated from your accepted error or transaction events. Generating issues does not cause Sentry to accept more events for you and does not directly impact your quota. Sentry does provide tools, however, to control the type and amount of error and transaction events that are accepted. Learn more in Quota Management.

For each issue, the page displays:

  • Issue type and description
  • Associated project
  • Issue timing, such as last and first time seen

For error issues, to see the stack trace of the latest event, you can hover over the issue title. You can also hover over the colored square to the left of the issue information to see the error level (error, info, fatal, warning, debug, or sample) of the latest event:

Error level icon

You can save your issue queries and access them later by clicking the the "Saved Searches" button in the header. Learn more in Saved Searches. You can also add issues data to your custom dashboards as widgets using the dataset selector.

When you click on an issue on the main Issues page, the Issue Details page for that issue is displayed. Learn more in Issue Details.

There are two categories of issues: error issues and performance issues. An error issue is a grouping of error events; a performance issue is a grouping of poorly-performing transactions. To learn more about each issue category and what kind of information is captured in their detailed view, check out our full Error Issues and Performance Issues documentation.

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 subset of all unresolved issues.
  • Regressed (is:regressed): All regressed issues; resolved issues that have come up again.
  • Archived (is:archived): All archived issues.
  • Escalating (is:escalating): All escalating issues; previously archived issues that have exceeded their forecasted event volume.

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

Change how issues are sorted in the issues stream by selecting from the sort dropdown:

Issue sort

  • Last Seen: The most recent events are shown first.
  • First Seen: The newest issues are shown first.
  • Trends: New issues and escalating issues (with event volumes trending upward) are shown first. Older issues and issues with fewer recent events are sorted lower. The ranking currently relies on three primary factors:
    • Relative volume: Escalating issues that have a higher recent volume (relative to their baseline) are ranked higher.
    • Absolute volume: Issues with more event volume are weighted more highly. Recent events are weighted more than old events.
    • Issue age: New issues are prioritized — an exponential decay factor halves the weight every 12 hours.
  • Events: Issues are sorted by total event volume.
  • Users: Issues are sorted by number of users affected.

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").