prometheus / prometheus/alertmanager

alertmanager messages lost due to high availability mode

Open
#4,179 4 comments 0 reactions 1 assignee View on GitHub

@SoloJacobs is already working on this.

Since Aug 25, 2026.

component/notify kind/support
Dominant language
Go
Stars
8.6k
Forks
2.5k
Avg merge
2d 6h
Merged PRs (30d)
61

Description

What did you do?

alertmanager irregular loss recovery message notification.

What did you expect to see?
alertmanager messages are not lost。

What did you see instead? Under which circumstances?
截屏2024-12-23 17 36 42

I deployed a cluster of 4 alertmanager nodes. The position of the alertmanager node that changes the picture printing log is 3, so it will wait 45s and then send the message. As shown in the picture, while he was sending the message, a new alarm entry came. Alertmanager No. 0 then sends a new alert entry, and then synchronizes the information to other nodes. When alertmanager No. 3 sent the message, he saw the new alarm, so he sent the old recovery, and then synchronized the old recovery to other alertmanager nodes, causing the recovery notification of the new alarm entry to fail to be sent.

  • Alertmanager version:
    v0.24.0

  • Logs:

ts=2024-12-21T06:13:49.106Z caller=dispatch.go:549 level=debug component=dispatcher aggrGroup="{}/{alertIndex!=\"\",alertObject!=\"\",business=\"tcloud-openplatform\",repeattime=\"ten_minutes\",serviceType!=\"\",tmplId!=\"\"}:{alertIndex=\"0\", alertgroup=\"cloudapp.biz-recsys.feature-updater.wg-binlog-live-qingmiao.327dbe35-1f5b.prod\", alertname=\"error_log\", serviceType=\"cloudApp\"}" msg=flushing alerts=[error_log[f6c3f84][resolved]]
ts=2024-12-21T06:13:49.106Z caller=dispatch.go:169 level=debug component=dispatcher msg="Received alert" alert=error_log[f6c3f84][active]
ts=2024-12-21T06:13:49.138Z caller=dispatch.go:169 level=debug component=dispatcher msg="Received alert" alert=error_log[f6c3f84][active]
ts=2024-12-21T06:14:49.105Z caller=dispatch.go:169 level=debug component=dispatcher msg="Received alert" alert=error_log[f6c3f84][resolved]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.