Hello Team, I am setting up some scheduled alerts...
# openobserve
k
Hello Team, I am setting up some scheduled alerts. Right now it seems pretty straight forward, but for some simple checks - I would like to avoid being notified multiple times of just a warning. We can use disk usage as an example of a VM. I would like to know that the usage hits 80% (example), but I don't want to be notified every 5 or 10 minute I would like to know that the usage hits 95% (example), which I'd like to get notified about, and if nobody picks it up anything - I would like to be notified again Right now it seems like alerts really only focuses on the critical alerts, adding a warning, but using the same schedule for notifications? Ideally it would be nice to be able to change the cooldown period depending on if its a warning or critical metric Best Regards
s
The repeat/cooldown interval is usually tied to the rule not to the severity inside a rule. So a single rule with both warning and critical thresholds ends up sharing one schedule. Easiest fix is to split it into two rules.
k
Agreed, I just dont see the option for changing critical to warning. When creating a new rule it allows me to add a warning level, but not remove the critical level
image.png