Alertmanager alerts arrive as typed events #1980

Closed
opened 2026-11-14 14:42:47 +00:00 by sam · 1 comment
Owner

Alertmanager's webhook delivers firing and resolved alerts to a source, and they become typed events (alert name, labels, annotations, status, start time) that triggers can filter on. A re-sent firing alert is a duplicate of the stored one; a new firing after a resolve is a new event; a resolve is linked to its firing event rather than treated as new.

Done when: a real firing and resolved alert appear as typed events, a re-send is deduplicated, and a trigger matches on an alert label.

Spec: R1, R5, R6.

Alertmanager's webhook delivers firing and resolved alerts to a source, and they become typed events (alert name, labels, annotations, status, start time) that triggers can filter on. A re-sent firing alert is a duplicate of the stored one; a new firing after a resolve is a new event; a resolve is linked to its firing event rather than treated as new. Done when: a real firing and resolved alert appear as typed events, a re-send is deduplicated, and a trigger matches on an alert label. Spec: R1, R5, R6.
sam added the hightask labels 2026-11-14 14:42:47 +00:00
sam added a new dependency 2026-11-14 14:42:58 +00:00
sam added a new dependency 2026-11-14 14:43:01 +00:00
Author
Owner

Verified on staging. Alertmanager's webhook lands on the prometheus source and every alert is stored as a typed alert event (alert name, labels, annotations, status, start time): 38 firing and 37 resolved so far, each resolve linked to its firing event rather than dispatched as new. A re-sent firing alert carries the same source event id and is counted as a duplicate by the store's unique constraint. A trigger filtering on labels.alertname matched its alert and started a run alongside the status-filtered trigger.

Verified on staging. Alertmanager's webhook lands on the prometheus source and every alert is stored as a typed alert event (alert name, labels, annotations, status, start time): 38 firing and 37 resolved so far, each resolve linked to its firing event rather than dispatched as new. A re-sent firing alert carries the same source event id and is counted as a duplicate by the store's unique constraint. A trigger filtering on labels.alertname matched its alert and started a run alongside the status-filtered trigger.
sam closed this issue 2026-11-15 17:29:59 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1980