Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add log level info to priority definition #10958

Merged
merged 2 commits into from
Aug 6, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/product/issues/issue-priority/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@ When Sentry receives an event, it assigns a priority to the issue based on the e

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.
- **High**: Issues that are likely to be actionable and require immediate attention, such as `ERROR` and `FATAL` events.
- **Medium**: Issues that are likely to be actionable and require attention in the near future, including `WARNING` events.
- **Low**: Issues that don't require immediate attention, including `DEBUG` and `INFO` events.

### Automatic Priority Updates

Expand Down
Loading