Resolving incidents
Manual vs automatic resolution.
Overview
Every incident ends up with a resolutionType of either automatic or manual. The server sets this depending on how the incident closed.
Automatic resolution
When a monitor that's down passes its next check, the active incident is closed automatically. A recovery notification fires to every channel attached to the monitor. resolutionType is recorded as automatic and the endTime matches the recovery check.
Manual resolution
The Incidents page shows an action menu on every active row with a Resolve manually option. Picking it opens a dialog with an optional Comment field.
- Navigate to Incidents in the sidebar
- Open the row menu on an active incident
- Click Resolve manually
- Optionally enter a comment describing what you did
- Confirm
The client calls PUT /api/v1/incidents/:id/resolve with the comment in the body. The incident's resolutionType is stored as manual along with the resolving user's email and, when provided, the comment. Resolved incidents appear in the lower table on the same page.
Manual resolution is useful when you've already fixed the issue out-of-band and don't want to wait for the next scheduled check.