Monitor-created incidents
Confirmed monitor failures create incidents with origin, cause, timing, and captured diagnostic context.
Incident response
Turn confirmed failures into coordinated response.
Track what failed, who or what created the incident, the affected monitor, notifications, updates, and recovery in one operational record.
Automatic and manual incidentsOperational timelinesRecovery notifications
Built for production work
The context your team needs, without unnecessary complexity.
Manual declaration
Operators can create an incident when impact is known before an automated monitor confirms it.
Lifecycle states
Move from investigation through monitoring and resolution while preserving accurate timestamps.
Incident timeline
Keep status changes, automated events, and operator updates in chronological order.
Customer updates
Publish appropriate incident information to connected status pages while private diagnostics stay internal.
Multi-channel notifications
Send incident and recovery messages to active email, Slack, or custom webhook destinations.
How it works
A clear operating workflow.
Detect
A monitor confirms failure or an operator declares impact.
Assess
Review cause, response evidence, affected service, and severity.
Update
Change status and communicate progress to the team and customers.
Resolve
Confirm recovery, close the incident, and retain its complete timeline.
Put this workflow into production.
Create a FaultPilot workspace, configure the feature, and keep the documentation nearby as your coverage grows.