bvandeusenandClaude Opus 5.5 734d313a54 feat(alerts): an acknowledgement is on the record, with who made it (#5463) ...

#5463 "Acknowledgements on record: an event and who did it", step 1 of
milestone 499 "Alerts you can trust". The live walk in #5461 found that
acknowledging changed only the alert's current state: once it resolved,
nothing said who had acknowledged it or when.

- alert_events.actor_id (migration 0040): the person behind a transition.
- Acknowledging writes a firing → acknowledged event by the acknowledger.
- A rule edit, disable or enable that resets an alert carries its actor
  (web and MCP alike).
- The history page notes "acknowledged by X" and "rule disabled by X"; MCP
  get_alert_history returns `by`.
- One usernames() helper in alerts.service, used by the active list, the
  history page and the MCP tools.
- docs/core/alerting.md: the state diagram no longer shows an acknowledged
  alert re-firing, and says what an event records.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-09 08:19:48 -04:00

..

alerting.md

feat(alerts): an acknowledgement is on the record, with who made it (#5463)

2026-10-09 08:19:48 -04:00

ansible.md

fix(ansible): overlapping runs: one per host, one per schedule, one action run per alert rule (#5158)

2026-10-06 21:24:51 -04:00

configuration.md

chore: rename project Roundtable → Steward

2026-04-25 16:20:14 -04:00

mcp.md

feat(mcp): connect card, MCP docs, and an end-to-end roles/audit test over HTTP

2026-10-06 08:25:41 -04:00

monitors.md

chore: rename project Roundtable → Steward

2026-04-25 16:20:14 -04:00