Open
Description
What did you do?
Peer
What did you expect to see?
When the alertmanager process is restarted, it should not be recognized as the old peer to the cluster. A possible solution would be an manual given peer name (like --cluster.peer-name=
), or the use of a deterministic peer name generation.
What did you see instead? Under which circumstances?
When the process is restarted for whatever reason, the alertmanager joins as a new peer. The old peer is present as "failed", which is not correct.
Environment
-
System information: n/a
-
Alertmanager version: version 0.20.0 (branch: HEAD, revision: f74be04)
-
Prometheus version: n/a
-
Alertmanager configuration file: n/a
-
Prometheus configuration file: n/a
-
Logs: n/a