Skip to main content
Obsy’s incident module covers the entire incident lifecycle: detection (from alerts or manual creation), coordination (Slack channels, role assignments, timelines), resolution, and follow-up (postmortems).

​
Incident lifecycle

Alert fires
    ↓
Auto-create rule matches (or manual creation)
    ↓
Incident created
    ↓
Slack channel opened (if configured)
    ↓
Roles assigned (commander, lead, comms)
    ↓
Timeline updated as team works
    ↓
Incident resolved
    ↓
Postmortem created

​
Incident fields

FieldDescription
TitleShort description of the impact
SeveritySEV1 (critical) → SEV4 (low)
StatusOpen → Investigating → Identified → Monitoring → Resolved
Affected servicesServices impacted, used to link status page components
TimelineChronological log of updates, Slack messages, and system events
Root causeLink to an RCA or manual notes
Slack channelDedicated channel created in your Slack workspace

​
Severity levels

LevelUse when
SEV1 — CriticalComplete outage, data loss, or severe customer impact
SEV2 — HighMajor feature unavailable for a significant number of users
SEV3 — MediumDegraded performance or a non-critical feature is down
SEV4 — LowMinor issue with a workaround available
Go to Incidents in the sidebar to see all open and recent incidents. Click any row to open the incident detail view with the full timeline, roles, and linked RCA.

Create an incident

Manually open an incident or let alerts do it automatically.

Slack channels

Auto-create a dedicated Slack channel for every incident.

Roles

Assign commander, lead engineer, and comms roles.

Settings

Configure auto-create rules, Slack settings, and notification channels.