IncidentRelay
Documentation

Incident Management

Version v2.3.1 · Updated
Interactive docs View on GitHub

Incident Management#

IncidentRelay 2.3 separates technical signal processing from operational incident response:

Alert -> AlertGroup -> optional Incident

An AlertGroup owns grouping, source state, ACK/resolve, notification, escalation, technical assignment and technical comments. A first-class Incident owns an independent operational workflow, priority, service context and operational assignee.

An AlertGroup can exist without an Incident. An Incident can exist without an AlertGroup, and one Incident can link multiple AlertGroups without merging their technical history.

APIs#

  • /api/alert-groups — technical AlertGroups.
  • /api/incidents — first-class operational Incidents.
  • 2.3 API migration — breaking endpoint and identifier changes.

The old /api/incidents == AlertGroup contract is not preserved.

2.3 collaboration boundary#

AlertGroup technical comments remain on AlertGroup. Legacy responders and stakeholders also remain AlertGroup-scoped during 2.3 and move to canonical Incident collaboration in the staged 2.5 work.