An Issue Alert When Condition Doesn't Trigger Reliably

[cobyeastwood183]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Create an Issue Alert with conditions provided (screenshot)
2. Throw a couple of errors, one error every minute or so

Expected Result

Alert should be triggered reliably by 1 event.

Actual Result

Alert is sometimes not triggered by 1 event (the HttpException in this case). Instead it seems to only fire reliably for 2, 3, 4, 5 events in the 1 min interval.

My Alert Page

My Issues Page

Product Area

Alerts

Link

No response

DSN

No response

Version

No response

[getsantry]

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

[cobyeastwood183]

https://sentry.zendesk.com/agent/tickets/143227

[rachrwang]

@cobyeastwood183 - if you remove that filter, does it work as expected? The way that that trigger works is that without any filters, we are evaluating for the alert as each new event is received. It should also work in setup you described, though will need more of the team's time to investigate why that isn't working as expected

[cobyeastwood183]

Removing the filter works (no 'When' conditions). But just expected this specific filter to trigger.

[ReneGreen27]

Related to internal ticket 148027 Ticket contains example links to related issues and events not triggered on Alert condition "Number of events in an issue is more than 1 in one day"

[minori-fh]

Related to internal ticket 148548. Ticket contains example links to related issues/ events not triggered on alert condition "Number of events in an issue is more than 1 in 5 minutes".