New issues always trigger alerts

[Nomango]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Follow the onboarding steps and create a project
2. There is a default alert rule named "Send a notification for high priority issues"
3. Send a event with medium priority

Expected Result

No alerts.

Actual Result

Received alert emails and webhook events for every new issue.

Product Area

Alerts

Link

https://looki.sentry.io/alerts/rules/capi-pet-sim/15731124/details/

DSN

https://a880e2af227783d2262a4067d0b73d13@o4508657645125632.ingest.us.sentry.io/4508657648795648

Version

No response

[getsantry]

Auto-routing to @getsentry/product-owners-alerts for triage ⏲️

[rachrwang]

@Nomango - if you would like to get alerted on every issue, please navigate to the alert rule and update your trigger to "a new issue is created"

[Nomango]

@rachrwang Maybe I didn't make it clear enough. The following is the feedback I have given on discord, and the reply I got is to submit an issue here.

I plan to report all exceptions with HTTP codes greater than 400 to Sentry, categorizing 4xx errors as medium priority and 5xx errors as high priority. I configured alerts to trigger only for high-priority issues. However, in practice, every time a new issue is reported, it triggers both email and webhook alerts, regardless of the issue’s priority. Am I missing something in my configuration?

[mifu67]

Hi @Nomango,

This seems like a bug. Thanks for letting us know about this issue! I did an initial investigation, and couldn’t identify a root cause. I’m going to move this ticket to our team's backlog to allocate more time to investigate the problem. Please reach out on this ticket with any follow-up questions you may have.

[haibo-looki]

@mifu67 Thanks for your reply!

If this issue is hard to reproduce, it might be easier to investigate the root cause using my account data (if you have access).

Here is the alert rule where the issue occurred. It is configured to trigger alerts only when the event priority is “high,” and no modifications have been made since the issue started.

In the alert trigger history, you can see a trigger on January 24. However, when checking the issue page, the event level is marked as “warning,” and the priority is “med.”

Alert trigger history

Alert email

Additionally, this alert is not an isolated case—every “med” issue triggers the same alert. I hope this additional information helps you in troubleshooting.