Issue Priority
Learn how Sentry prioritizes issue actionability.
Issue priority sorts the issues Sentry receives into High, Medium and Low priority buckets. This helps you identify and address critical, high-priority errors that may be impacting your application's functionality and user experience first.
When Sentry receives an event, it assigns a priority to the issue based on the event's log level (for error issues) or actionability (for non-error issues like performance).
There are three discrete priority levels for issues in Sentry:
- High: Issues that are likely to be actionable and require immediate attention.
- Medium: Issues that are likely to be actionable and require attention in the near future.
- Low: Issues that don't require immediate attention.
In addition to the log level or actionability, the enhanced priority calculations will consider factors such as the error message, whether or not the error is handled, and historical actions taken on similar issues, when determining the priority of an issue for Python or JavaScript projects.
Sentry continuously monitors the volume of events for each issue. If there's a surge of events for a particular issue (it escalates), its priority level will be automatically bumped up. See the escalating issues algorithm for more information on how escalations are identified. When an issue de-escalates, its priority will go back down to the previous level.
You can update issue priority manually at any time, either from the issue details page or from the issue stream. But once an issue's priority has been changed manually, it will no longer be automatically adjusted if the event volume escalates.
By default, the issue stream on the Issues page filters out low-priority issues. If you'd like to be able to see low-priority issues, you can set your default search to include them.
When viewing the "Prioritized" tab, you can quickly triage issues by using the priority dropdown. Low-priority issues will disappear from the "Prioritized" tab once their priority is updated.
You may also update the priority level of multiple issues at once by selecting them and using the bulk action dropdown.
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").