-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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 rules for all project #30059
Comments
Routing to @getsentry/ecosystem for triage. ⏲️ |
Routing to @getsentry/workflow for triage. ⏲️ |
@kamilic thanks for the request. We've heard this quite a few times -- I'll make sure we reach out directly or update this thread when we start working on it. |
@adhiraj Thanks for your feedback. Nice to make some helps for you. I am looking forward to this new feature. |
@adhiraj There are any progresses on this feature? |
@kamilic I'm using this script as a workaround for now. Following this issue though |
Any updates on this? This would be super useful for our use-case too. |
So much yes, please! |
:( |
My organization would also love this to be able to quickly get notified if there's a surge of errors reported from any of the sentry projects that would otherwise eat up our error quotas. Right now any project that don't have correctly configured alerts could be missed completely until an organization admin notices the "You've reached 80% of your error quota limit" email that Sentry sends. |
Another way to work around this is to automate the alert rules using terraform sentry_issue_alert resources. |
I have the same problem FWIW. Our alerts are conceptually very generic and we want them to apply to all projects. It is strange that environments get one treatment and projects get a different one? |
Routing to @getsentry/product-owners-alerts for triage ⏲️ |
Any plans to add this? SRE team at my org wants to have a Slack channel where issue alerts from all projects are coming in. |
@isabellaenriquez @jangjodi Pinging you folks here given your comments on #63173. |
@PrayagS Agree that this would be a useful feature. However, I don't have a timeline for this. |
Hi @leedongwei - wanted to check in on this request and see if it's gained traction? |
Hey @kpujjigit / all, just a quick update on this - we are actively working on this feature! Our hope is to really simplify the process of defining an alert, then applying those alert rules on multiple projects. We're also working on a similar feature on the notification side of alerts, where you can share notification configurations between different alert rules. We don't have timelines on when this project will be completed, but we'll keep ya up to date as we approach the release -- but feel free to message this issue again in a couple weeks and we'll hopefully have a clearer timeline then. |
Heya @saponifi3d thanks for that promising update about a month back, is there any further progress or ETA you can share? |
Hey @kpujjigit! Yeah, excited about this too! I was just writing some migrations for the feature today! 🎉 Unfortunately, I'm still not sure of an ETA for this feature to land yet, but it probably won't be for a while. Right now we're working on some underlying changes to the alerting experience to be able to support this feature and allow us to improve the alerting experience as a whole. The good news is that we are actively working on it! Hope we can share updates soon 🤞 feel free to keep messaging on this thread if you have any questions. |
Problem Statement
Our on-premises sentry instance contains about ~100 projects and its alert rule.
It is hard to maintain alert rules if I want to edit condition. (I need to keep all project to same rule, so I need to propagate manually to the rest ~100 projects).
Solution Brainstorm
The text was updated successfully, but these errors were encountered: