getsentry / getsentry/sentry

Performance Issues Triggering High Priority Alerts Despite All Being Low Priority

Open
#78,668 6 comments 0 reactions 0 assignees View on GitHub
Bug Product Area: Alerts Sync: Jira
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

Create an alert as the below:
![Image](https://github.com/user-attachments/assets/6b5301b6-4e67-4d21-b212-f99bde191dfc)

Observe that performance issues that are low priority are triggering the alert:
![Image](https://github.com/user-attachments/assets/37c213fb-e635-481e-9ea9-442c527344c0)
![Image](https://github.com/user-attachments/assets/1f5f972b-c4d4-4ea9-ada9-add24e15c89a)

As a workaround for now, the user has filtered by IF "The issue's category is equal to Error." Customer also reported that performance issues should appear in the alert preview.

Alert linked in Jira ticket.

### Expected Result

Low priority performance issues do not trigger a "Send a notification for high priority issues" and the alert preview include performance issues.

### Actual Result

Low priority performance issues are trigger a "Send a notification for high priority issues" and the alert preview does not include performance issues.

### Product Area

Alerts

### Link

_No response_

### DSN

_No response_

### Version

_No response_

┆Issue is synchronized with this [Jira Improvement](https://getsentry.atlassian.net/browse/FEEDBACK-2311) by [Unito](https://www.unito.io)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.