Skip to content
Design System
GitHub

Incidents

When something goes wrong at a site: the queue of incidents, and one incident from declared to resolved.

Overview

When to use

  • Operations teams that own what happens after an alarm.

Use something else

  • A single alarm to acknowledge: the Alarm component.

Blocks

Incident queue

Open incidents, unowned first, then by severity and age; severity has a shape and a number, and nobody-owns-it is a button.

Install
npx shadcn add @syncrobotic/incident-queue

Incident

One incident: its state as steps, the facts, and updates newest first; posting an update can move it on.

Install
npx shadcn add @syncrobotic/incident-detail

Usage rules

  • Unowned first, then by severity, then by age.
  • Severity is a number and a shape; only the levels that stop or slow work are coloured.
  • Every state change is an update in the record, with who and when.