Alerts from any source, not only Alertmanager: an event with a lifecycle (opened, acknowledged, resolved, suppressed), a severity, a target and what is working it. Core stays vendor-free, so a source declares alerts and the alerts module owns the lifecycle.
Table in the alerts module's own schema; API for list, detail and state transitions; page showing what is open now, what is being worked and what resolved, filterable by source, severity and target.
Fed from events: a source's alert-typed event opens or resolves an alert; Archie's own acknowledgement is a change, recorded like any other (audit, R42).
A trigger can filter on alert state, so a resolved alert stops the work that a firing one started.
Done when: an Alertmanager alert appears on its own page with its lifecycle, a resolve closes it, and a source that is not Alertmanager produces alerts through the same path.
Alerts from any source, not only Alertmanager: an event with a lifecycle (opened, acknowledged, resolved, suppressed), a severity, a target and what is working it. Core stays vendor-free, so a source declares alerts and the alerts module owns the lifecycle.
- Table in the alerts module's own schema; API for list, detail and state transitions; page showing what is open now, what is being worked and what resolved, filterable by source, severity and target.
- Fed from events: a source's alert-typed event opens or resolves an alert; Archie's own acknowledgement is a change, recorded like any other (audit, R42).
- A trigger can filter on alert state, so a resolved alert stops the work that a firing one started.
Done when: an Alertmanager alert appears on its own page with its lifecycle, a resolve closes it, and a source that is not Alertmanager produces alerts through the same path.
sam
added the featurehigh labels 2026-11-16 02:22:02 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Alerts from any source, not only Alertmanager: an event with a lifecycle (opened, acknowledged, resolved, suppressed), a severity, a target and what is working it. Core stays vendor-free, so a source declares alerts and the alerts module owns the lifecycle.
Done when: an Alertmanager alert appears on its own page with its lifecycle, a resolve closes it, and a source that is not Alertmanager produces alerts through the same path.