This message was deleted.
# general
a
This message was deleted.
a
This is on rancher 2.7.1
r
Hello, This is the namespace that your alerteManagerConfig is deployed. It will be added automatically when you create an AlertManagerConfig This matcher mean that only the Alerts of the objet that are in the same namespace as the alertemanagercinfig ( vault) will be send.
Currently on the rancher-monitoring-101.0.0+up19.0.3 version, with AlertManagerConfig, only alert on the alertemanagerconfig namespace will be send. This issue is solved on version 102.0.0+up40.1.2 dev.
b
@rich-electrician-53678 Is that correct? Seems the `alertmanagerConfigMatcherStrategy`flag that fixes this was added in v.061.1 but ranchers mirrored charts are lagging behind and still on v0.59.1? https://github.com/rancher/charts/blob/dev-v2.7/charts/rancher-monitoring/102.0.0%2Bup40.1.2/values.yaml#L2646 https://github.com/prometheus-operator/prometheus-operator/issues/3737#issuecomment-1326667523
r
Hi, I have tested the method that i'am talking about, it works Well. You juste need to use the alertemanagerconfiguration available in the chart version 102.0.0+up40.1.2 for rancher-monitoring and rancher-monitoring-crd
b
Thanks, will give it a shot then 👍