Incidents
Track, manage, and communicate about service disruptions. FlareWarden automatically creates incidents when monitors detect issues, and you can also create manual incidents for planned or undetected events.
Incident Types
Incidents are categorized based on how they were detected
Uptime
HTTP endpoint is unreachable or returning errors
Content
Page content doesn't match expected pattern
SSL
Certificate expired or validation failed
DNS
DNS resolution failed or records changed
Dependency
External dependency or API is unavailable
Manual
Created manually for undetected or planned issues
Incident Lifecycle
Understanding the stages of an incident
Started
Issue detected
Ongoing
Being investigated
Resolved
Issue fixed
Automatic Detection: For monitored endpoints, incidents are automatically created when checks fail and resolved when the service recovers. Manual incidents must be resolved manually.
Creating Manual Incidents
Report issues that aren't automatically detected
Sometimes you need to report an incident that your monitors didn't catch, or communicate about an issue before automated monitoring detects it. Manual incidents let you do this.
When to Use Manual Incidents
- Partial outages affecting some users but not triggering monitors
- Performance degradation noticed by customers
- Third-party service issues affecting your application
- Proactive communication about known issues
How to Create
Navigate to the monitor
Go to the monitor details page for the affected service
Click "Report Incident"
Find the button in the monitor actions area
Add incident details
Provide a title and description explaining the issue
Select severity
Choose Critical (service down) or Degraded (partial impact)
Incident Severity
How severity affects monitor status and notifications
The service is completely unavailable. Monitor status changes to DOWN.
- • Status page shows service as down
- • Immediate notifications sent
- • Uptime calculations affected
Service is available but experiencing issues. Monitor status changes to DEGRADED.
- • Status page shows degraded performance
- • Notifications sent to subscribed users
- • Tracked separately from full outages
Resolving Incidents
Automatic and manual resolution options
Automatic Resolution
Incidents created by monitors are automatically resolved when:
- • The endpoint returns a successful response
- • Content matches the expected pattern again
- • SSL certificate issues are fixed
- • DNS records resolve correctly
Manual Resolution
To manually resolve an incident:
- Navigate to the incident in your dashboard
- Click the "Resolve Incident" button
- Optionally add a resolution message
- Recovery notifications will be sent automatically
Duration Tracking: When an incident is resolved, FlareWarden automatically calculates and records the total duration. This data is used for uptime reporting and SLA calculations.
Incident History
View and analyze past incidents
FlareWarden maintains a complete history of all incidents for each monitor. Use this data to identify patterns, improve reliability, and generate reports.
Available Information
| Field | Description |
|---|---|
| Start Time | When the incident was first detected |
| End Time | When the incident was resolved |
| Duration | Total time the incident was active |
| Type | Category (uptime, content, SSL, DNS, dependency, manual) |
| Severity | Critical or Degraded |
| Error Message | Technical details about what went wrong |
Status Page Integration
How incidents appear on your public status page
When a monitor attached to a status page experiences an incident, the status page is automatically updated to reflect the current state.
- Component status updates in real-time via SSE
- Subscribers receive email notifications
- Incident history visible on the status page
- Recovery notifications sent when resolved