Repository navigation
Greater flexibility when creating alert conditions #54732
Description
Problem Statement
Right now, when creating a conditional alert, you have two choices: match all conditions, or match any condition. This prevents conditions like if animal = dog and fur = brown and breed in [catahoula, pit bull, chow] and if (animal = dog and fur = brown) or (animal = cat and fur = white) from being applied.
One example use case, submitted by a user, is to have one of the conditions be a match to one of several different tags (similar to my first example above), but one can imagine more complex conditions being desired.
Right now, the only workarounds are a) use the SDK to add an alert-specific tag to events which should trigger the rule, b) create multiple rules, which are almost but not quite the same, or c) build an internal integration to forward the alert data to some other service, which can then run the full conditions. Obviously, none of these is great.
Solution Brainstorm
Simpler solutions, which would handle the user's case in the linked issue:
- In addition to a match being able to be
equals,starts with,contains, etc., add anis one ofoption, which then would take a comma separated list of values. - Similar to the above, but add a
matches regexoption.
More complicated solution:
- Allow combining conditions more flexibly with
ANDs andORs. I get that in theory this could allow a user to create a frankenstein rule out of rules which really should be separate, but it would allow for a one-rule-per-resulting-action paradigm, which actually IMHO isn't a terrible way to think about alerts.
Product Area
Alerts
Activity
getsantry commentedon Aug 14, 2023
Routing to @getsentry/product-owners-alerts for triage ⏲️
[-]Great flexibility when creating alert conditions[/-][+]Greater flexibility when creating alert conditions[/+]jalaziz commentedon Oct 21, 2023
Our team would absolutely love this.
We want to be able to create an alert rule for some subset of environments, but ALSO use event attribute filters to enforce a level filter.
Unfortunately, it seems the only option is creating multiple alert rules which gets very painful quickly as we have multiple services that all the same alert rules.
karol-wons-deel commentedon May 2, 2024
Upvoting this idea 👍
At deel.com we also wanted to build an alerting system based on URL regex matches
22 remaining items
liam-eci commentedon Oct 21, 2025
@saponifi3d, great news. When can we expect to see these improvements? Any prediction helps. This is causing a lot of duplications on our alert rules - and the system is limited to 100 rules.
saponifi3d commentedon Oct 21, 2025
@liam-eci 👋 helloooo from the OR conditions ticket!
so.. 😅... my manager dislikes this answer too, but.. I'm not really sure about when we'll be able to flip this on.
We've started internally testing and getting some great feedback. That also means, more things for us to do before we release to a wider audience. Also, we're a little nervous about some larger changes because we want to make sure to get this right; so we're going to make a post with screen shots and ask y'all for feedback too (I believe that will be up later today).
Hopefully it helps know that we're on the last mile of the project, and y'all will be able to see some of these things soon. 🫶
ReneGreen27 commentedon Oct 22, 2025
Upvote for OR conditions contained in internal ticket #164451
souredoutlook commentedon May 22, 2026
We shipped the ability to do the following:
We also support multiple IF THEN blocks per alert.
Closing as done.