Replies: 1 comment
-
In your example, what does |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Originally posted on grafana/grafana and posting here as reported to be:
Copy paste of the original message:
In notifications policies, my understanding of
group_interval
is the amount of time to wait before sending any notification for an alert that changed.Let's assume I have an a notification policy configured like this:
And an alert with same name but being triggered for various pods (I am running in k8s).
If the alerts gets triggered for pod A only, then within 10s I will get a notification with
pod=A
in labels.If then pods B and later pod C are triggering the alert, then no notification will be sent for then within 5 minutes. Only after 5 minutes it will be sent. In my case, I would like this 5m setting to be higher, like 1h to avoid spam of alerts when the list of pods is changing quite a lot for some time. So I would set
group_interval: 1h
.But instead of the above new pods added to the alert I have the use case of the alert being resolved, it will only send a notification after
group_interval: 5m
orgroup_interval: 1h
depending on what I have configured. And I would like this to be lower.Hence my requests:
group_interval
split intogroup_interval
andresolution_interval
.Indeed, I understand some might not want to resolve too quickly to avoid up/down effect in case of instabilities.
But I have a metric in my case that is triggered during rollout restart and that has many updates for some time (maybe 30 to 60 minutes) and get spammed with notifications that I have to silence. I would prefer having one ... but be notified asap (understand 1 minute for example) if the alerts gets resolved.
I hope the above makes sense, let me know.
Thank you
Beta Was this translation helpful? Give feedback.
All reactions