Incident Management
Create, manage, and resolve incidents to keep your users informed about service disruptions.
Incident Lifecycle
Each incident progresses through a defined lifecycle from detection to resolution:
Incident Statuses
Issue is being looked into - Initial detection of a problem
Root cause has been found - After determining what's wrong
Fix deployed, watching for issues - After implementing a fix
Issue is completely fixed - Incident is over
Impact Levels
Complete service outage
Example: Website is down
Some features unavailable
Example: Login is broken
Performance issues
Example: Slow response times
Minimal impact
Example: UI glitch
Creating Incidents
Navigate to Admin → Incidents
Click Create Incident
Fill in title, status, impact
Select affected components
Click Create
Best Practice
Create incidents as soon as you're aware of an issue, even before you know the root cause. Users prefer transparency over silence.
Posting Updates
Keep users informed by posting regular updates:
Good Update Example
Status: Identified
We've identified the root cause as a database connection
pool exhaustion issue. Our team is working on implementing
a fix. We expect to deploy the fix within the next 30 minutes.
Affected services: API, DashboardResolving Incidents
Good Resolution Message
Status: Resolved
This incident has been resolved. The issue was caused by
a database connection pool exhaustion during a traffic spike.
We've increased the pool size and added better connection
handling to prevent this in the future.
Duration: 45 minutes
Impact: API and Dashboard were unavailable
We apologize for any inconvenience caused.Notifications
When incidents are created or updated, subscribers receive notifications:
Display Position
Configure where active incidents appear on your status page:
| Position | Description | Best For |
|---|---|---|
| Top (Default) | Above overall status | Maximum visibility |
| Below Status | After overall status | Balanced visibility |
| Below Components | After component list | Secondary focus |
Component Status Impact
When an incident is linked to components, those components (and their parent groups) automatically show "Partial Outage" status until the incident is resolved.
API Access
Create incidents programmatically using the API:
POST /api/v1/incidents
{
"title": "Database connectivity issues",
"status": "investigating",
"impact": "major",
"message": "We are investigating reports of database issues.",
"componentIds": [1, 2]
}