Just found the issue. I should use mute_time_intervals and not inside match
- group_by:
- alertname
- severity
- env
match:
type: aws-alarm
mute_time_intervals:
- test
receiver: aws-alarm
On Thursday, May 20, 2021 at 2:14:04 PM UTC-5 Bruno Criado wrote:
> I'm testing the new feature
> <https://github.com/prometheus/alertmanager/pull/2393> of muting an event
> based on time but looks like it's not working as expected yet.
> ...
> - group_by:
> - alertname
> - severity
> - env
> match:
> type: aws-alert
> mute_times: test
> receiver: aws-alert
> continue: true
> ...
> mute_time_intervals:
> - name: test
> time_intervals:
> - weekdays: ['monday']
> times:
> - start_time: '09:00'
> end_time: '09:01'
> ...
>
> As you can see, I've declared the time interval (test) and linked with my
> receiver, but I'm not able to receive any alert when the time interval is
> declared on the receiver (I'm testing on Tuesday). So if I remove the
> mute_times I receive alerts as expected.
>
> Has someone already tested that feature? Is it working properly?
>
--
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/e07e5e9b-2f9c-466b-9c63-6433f7ee2082n%40googlegroups.com.
