Alertmanager's alertmanagerConfigMatcherStrategy issue #5038
Description
I've tested this PR, and there is another logical error.
When the config of the Alertmanager got generated, since we don't use the Alertmanager CRD, we built it with the defaults:
alloy/internal/component/mimir/alerts/kubernetes/events.go
Lines 178 to 180 in 8c0090c
And it breaks the config, since it implicitly adds the
matchers:
- namespace="mimir"
to the main route:
...
routes:
- receiver: mimir/alertmanager-config/sre-alerts
group_by:
- alertname
- cluster
matchers:
- namespace="mimir" #<---- the issue, since we care only about the alerts from the mimir ns
continue: true
routes:
- receiver: mimir/alertmanager-config/other-alerts
matchers:
- cluster="staging"
- project="project1"
continue: false
repeat_interval: 12h
...
Because we don't use the Alertmanager CRD, where we can set the alertmanagerConfigMatcherStrategy.
Originally posted by @artemlive in #5010 (comment)