Ok, I will answer myself.
The way to do this is with continue, continue will permit firing to more
than one receiver. I had mistakenly thought that continue would simply
continue without firing at first match. Alertmanager is deceptively
powerful. The only missing piece is a piece of UI to manage the list of
pager numbers for on-call rotation that can now be defined in the
alertmanager (offhoursgroup).
# Select receiver based on time of day
- match:
severity: 5
receiver: daygroup
mute_time_interval: offhours
continue
- match:
severity: 5
receiver: offhoursgroup
mute_time_interval: workhours
Then I just need to manage/automate who is in the offhoursgroup based on
the rotation schedule.
This would work for my purposes.
Le mardi 29 juin 2021 à 14:14:42 UTC-4, xkilian a écrit :
>
> Can a route use a mute_time_interval as a route matcher criteria?
>
> routes:
>
> # Select receiver based on time of day
> - match:
> severity: 5
> receiver: daygroup
> routes:
> - match:
> mute_time_interval: offhours
> receiver: offhoursgroup
>
>
> (Not sure the indentation is perfect)
>
> Thank you,
>
> xkilian
>
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/7183aa04-a6ea-419a-a4bd-9f327dd1e393n%40googlegroups.com.