Open githubjakob opened 4 months ago
Auto-routing to @getsentry/product-owners-alerts for triage ⏲️
@githubjakob , I'm not able to reproduce what you're seeing, though once difference is that I tried it with event.type:error only. Can you try changing that filter, and seeing if anything changes on your end?
@rachrwang Thank you for your response! I was already in contact via support with one of your colleagues. They said they will attach more information from our conversation.
I was testing again with new Sentry accounts and I think I could only reproduce the issue in a EU account. In US it works for me as well.
I tested with these 2 accounts (both keys are disabled again):
https://36052ba7e35c270ca199c709f6c2d264@o4507581995089920.ingest.us.sentry.io/4507581996793856 https://f7038ac95a1849ac9440ef80b2295d66@o4507582736039936.ingest.de.sentry.io/4507582737743952
I hope from the screenshots you can see that in the EU account the alert with the filter for is:unresolved is not triggered even though it is triggered in the US account.
On the left you have the EU, on the right the US:
Both accounts have issues:
One issue is marked as "archived", so it does not appear in the issues when filter for "is:unresolved":
There are 2 alerts, both with threshold of 0, one with no filter, the other with filer "is:unresolved"
Both alerts should be triggered:
See the config for both alerts:
This is a continuation from this Zendesk ticket. Added the information gathered in the shadow ticket.
Thank you! I'll work with the eng team to see if we can get this prioritized
Are there any updates on this? @rachrwang
Hey @githubjakob We've confirmed the bug and have some other related tickets to this. I believe we're prioritizing these tickets now and will hopefully have an update for you soon.
thank you for your patience! 🙏
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Set up the feature as described here https://sentry.io/changelog/removing-archived-issues-from-metric-alerts/
Having this filter is crucial for us, because we have a lot of issues in resolved status that we want to exclude from triggering the alert. Without this filter, 99% of the times the alert is a false positive for us, and we have to manually look into it to distinguish from real alerts.
Expected Result
Alert is triggered
Actual Result
Alert is not triggered
Product Area
Alerts
Link
https://xxx.sentry.io/alerts/wizard/?referrer=alert_stream&project=xxx
DSN
No response
Version
No response
┆Issue is synchronized with this Jira Improvement by Unito