-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Alert once per environment per issue #21612
Comments
Agreed this would be useful. In the meantime here's an approximate workaround:
The edge case here is that if an issue is first seen in an environment more than 30 days after it was created, it won't alert. |
@adhiraj not sure I follow? We don't have an "IF" clause, unless I'm misunderstanding you? |
@cpressland are you running self-hosted sentry? This is currently on the cloud version, but we'll be releasing it to self-hosted in a few weeks. |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
Related issue: #64354 |
Proposed solution: we add a new IF condition for the "every event trigger" that says: "First time seen in {environment}", where {environment} is a dropdown |
Summary
An additional option to send alerts based on first time an issue is seen in a given environment instead of just the first time the issue is seen.
Motivation
We use Microsoft Teams for alerting, we currently have the following setup in Sentry Alerts:
We'd like to instead only fire alerts the first time an issue is seen within a specific environment, however, the following workflow doesn't work:
With this setup we only ever see a single alert regardless of environment. If an issue first occurs in Staging, we'll never see a second alert and third alert in the Dev or Production channels. Instead, the alerting rules should give us the flexibility to alert once per env per issue.
The text was updated successfully, but these errors were encountered: