On Thursday, 27 February 2025 at 13:44:07 UTC Al wrote: The main purpose of this kind of configuration would be to adress the following : - have a single cluster to which silences to be managed
Another way to address this is to have a front-end which manages all the alertmanager clusters. karma <https://github.com/prymitive/karma> is one, alerta.io is another. You can manage silences globally from one panel (at least, I know karma can; I have not tried alerta). - to ensure global redundancy if one region should become unavailable If the region has completely failed, then presumably there's nothing within that region that is worth alerting on anyway. You can monitor the alertmanager cluster in one region from a prometheus in another region, to get an alert of that failure mode. However, the simplest solution would be to have a single alertmanager cluster, spread across AZs in a single region; all the other prometheuses send their alerts to this cluster. Alerting is low traffic and I don't see a particular reason to have a separate alertmanager cluster in every region. You can test that you can reach prometheus in every other region, and then you have high confidence that prometheus in those regions will be able to contact the central alertmanager. -- 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 prometheus-users+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/prometheus-users/7db1a04d-7d2a-4bc4-a108-d9c2e6cdeb31n%40googlegroups.com.
