Unmatched events are kept and grouped #1994

Open
opened 2026-11-14 14:42:49 +00:00 by sam · 3 comments
Owner

Events no trigger matched are stored and grouped by source, event type and key fields, and each new group starts a draft. Events caused by Archie's own deliveries are linked to their run and never become proposals.

Done when: the first disk-pressure alert produces a draft, repeated unmatched events appear as one group, and Archie's own incident updates never produce proposals.

Spec: decision tree 8.1, R5, R9.

Events no trigger matched are stored and grouped by source, event type and key fields, and each new group starts a draft. Events caused by Archie's own deliveries are linked to their run and never become proposals. Done when: the first disk-pressure alert produces a draft, repeated unmatched events appear as one group, and Archie's own incident updates never produce proposals. Spec: decision tree 8.1, R5, R9.
sam added the featuremedium labels 2026-11-14 14:42:49 +00:00
sam added a new dependency 2026-11-14 14:43:00 +00:00
Author
Owner

From the 2026-11-16 module review: dispatch records matched = false and stops, so there is nothing to group by and no way to tell Archie's own notifications from outside events.

Record two things at intake: provenance on every event (so Archie's own deliveries are excluded where they arrive, never filtered later), and a group key from the source, event type and key fields. A group is then a row a draft hangs off, and this issue is a read over groups rather than a scan for a false flag.

From the 2026-11-16 module review: dispatch records `matched = false` and stops, so there is nothing to group by and no way to tell Archie's own notifications from outside events. Record two things at intake: provenance on every event (so Archie's own deliveries are excluded where they arrive, never filtered later), and a group key from the source, event type and key fields. A group is then a row a draft hangs off, and this issue is a read over groups rather than a scan for a false flag.
Author
Owner

Landed in 50b75f698 and on staging (migration 00029). At intake each event records whether it is an echo of one of Archie's own deliveries (matched by the external id the connector returned from Deliver, against the source's connector) with the run that sent it, plus a group key: sha256 over source, event type and the source's key fields (PUT /api/sources/{name}/key-fields, default alertname, name, labels, severity, service, host, instance). Own echoes skip trigger matching and never group. Unmatched events upsert a group at dispatch; GET /api/groups lists groups whose proposed trigger doesn't exist yet, and the Unmatched page creates the trigger. Not yet shown: the demo path (first disk-pressure alert producing a draft), no key-field editor in the dashboard, and an echo that arrives before Sent records the id is not recognised.

Landed in 50b75f698 and on staging (migration 00029). At intake each event records whether it is an echo of one of Archie's own deliveries (matched by the external id the connector returned from Deliver, against the source's connector) with the run that sent it, plus a group key: sha256 over source, event type and the source's key fields (PUT /api/sources/{name}/key-fields, default alertname, name, labels, severity, service, host, instance). Own echoes skip trigger matching and never group. Unmatched events upsert a group at dispatch; GET /api/groups lists groups whose proposed trigger doesn't exist yet, and the Unmatched page creates the trigger. Not yet shown: the demo path (first disk-pressure alert producing a draft), no key-field editor in the dashboard, and an echo that arrives before Sent records the id is not recognised.
Author
Owner

Shown on staging after #2008: the first alert with no trigger formed one group with a proposed trigger and a draft. Not yet shown: repeats joining the group, and an own-delivery echo being excluded. The proposed filter repeats alertname (top level and labels.alertname) because both are default key fields.

Shown on staging after #2008: the first alert with no trigger formed one group with a proposed trigger and a draft. Not yet shown: repeats joining the group, and an own-delivery echo being excluded. The proposed filter repeats alertname (top level and labels.alertname) because both are default key fields.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1994