Replies: 1 comment
-
Hello, as you may have heard, we are transitioning away from using discussions to discuss feature requests. We are migrating this discussion to an issue and closing the discussion. The issue is #82845. Feel free to continue the discussion around this there. Thank you! |
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
-
Currently, Notification Policies can only match on labels.
So, for example, I can easily say: Send alerts with
host=foo
to contactbar
.However, this will result in all statuses going to
bar
which may not be desirable -bar
may want to receiveFiring
andResolved
but notDataSourceError
.As a real-world example, I have the following setup:
severity=critical
and send to PagerDuty (to generate a page)However, if my datasource is unavailable (for example, down for a full filesystem backup) the alert will go to status
DataSourceError
and generate a page.This might be quite unwelcome at 2am. Mute timings can't be used for this, because you do want to receive a page if the thing being monitored is genuinely on fire.
It is possible to override this behaviour on the alert:
But that's not necessarily desirable:
It might be possible to hack something similar together by using a string template to set a label value (using
{{ .Status }}
) but it'd be nice to have a way that's less involved and doesn't require customising every current and future alert.Beta Was this translation helpful? Give feedback.
All reactions