Open osxd opened 10 months ago
Assigning to @getsentry/support for routing ⏲️
Routing to @getsentry/product-owners-alerts for triage ⏲️
Thanks for the feature request, I've added it to our team's backlog. You might also consider creating a custom webhook to handle additional logic for the time being that would forward to your preferred channels.
Problem Statement
I'm looking for a bit more advanced rules in the Alert settings.
We have WHEN → IF → THEN chain, and we filter at each step what happened, if ALL or ANY condition has been met, and finally declare what to do
this would work for scenarios when i have simple conditions, and I'm looking for the following thing:
problem is in 2. – i need either several IFs statements, or having something like this:
what we will get: ability to have less alerts set up, and then allow to throttle/debounce that alerts per their priority levels. e.g. we don't need immediate notification is slack most of times, but we would appreciate some high spikes
⚠️ also, looks like any event in WHEN would trigger it's unique notification, would be cool to have them aggregated in one "big" slack notification (especially if delivery set to once per 24 hours / week or so)
Solution Brainstorm
Looks like we can also achieve similar behaviour by creating multiple alerts, when we can define levels
this would add a bit of toll of maintenance of the alerts, but can be a solution
other solution would be allowing chaining multiple IF statements
WHEN X → IF any/all of A,B,C conditions → IF any/all of C,D,E conditions → IF .... → THEN
of course, disputable, but would help to have 1 alert per 1 type of Thershold (last option – we decide then how often this alert to be triggered
Product Area
Unknown
┆Issue is synchronized with this Jira Improvement by Unito