Documentation
Incidents
Incidents are an ops layer on alerts — not a second monitoring engine. Track investigation state without inventing severity.
Lifecycle
Typical flow: investigating → identified → monitoring → resolved. Acknowledge and resolve (with optional RCA). Escalation tasks can run when configured via Trigger workers.
Status pages
Incidents may publish to a workspace status page when publishToStatusPage is enabled. See Status Pages.
Plans
Requires Pro+ (incidents). Free has no incident desk.
Limitations
- Does not replace vendor paging rotations (PagerDuty native, etc.).
- Open count is observed — empty means quiet, not “fake zero green.”