Add log level info to priority definition (#10958)

* Add log level info to priority definition * Update docs/product/issues/issue-priority/index.mdx Co-authored-by: vivianyentran <[email protected]> --------- Co-authored-by: vivianyentran <[email protected]>
getsentry · Aug 6, 2024 · 257526c · 257526c
1 parent d601c3a
commit 257526c
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/product/issues/issue-priority/index.mdx b/docs/product/issues/issue-priority/index.mdx
@@ -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.
 
 ### Enhanced Issue Priority