Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upHandle multiple alertmanagers #822
Comments
This comment has been minimized.
This comment has been minimized.
|
We are about to start more detailed planning of a highly available Alertmanager. This will also involve Prometheus being aware of all Alertmanagers for the scenario you described. The latter alone is not the full story so this will certainly take a while. |
This comment has been minimized.
This comment has been minimized.
|
Only medium-term. I'm in the middle of creating a prometheus proof-of-concept, and noticed this when I was setting up the cluster. |
This comment has been minimized.
This comment has been minimized.
|
It's right on top of our list. Keep an eye on the mailing list if you are interested – a design doc might be posted there sooner or later. |
brian-brazil
added
the
feature-request
label
Dec 16, 2015
fabxc
added
kind/enhancement
and removed
feature request
labels
Apr 28, 2016
This comment has been minimized.
This comment has been minimized.
brian-brazil
closed this
Jul 2, 2016
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
swsnider commentedJun 22, 2015
In order to handle network partitions and down machines, it would be helpful if Prometheus could be given multiple alertmanagers it can talk to, so that if the one it picks doesn't respond in a timely fashion (or fails), it could try one of the others.