Event types and statuses
Incidents
An incident represents an unexpected event that affects service availability. Incidents have the following lifecycle statuses:| Status | Description |
|---|---|
| Investigating | The team is aware of the issue and investigating the root cause |
| Identified | The root cause has been identified and a fix is being developed |
| Monitoring | A fix has been implemented and recovery is being monitored |
| Resolved | The issue is fully resolved and service is back to normal |
Maintenance
Maintenance represents a planned service change event used to notify users in advance of potential service impact. Maintenance has the following lifecycle statuses:| Status | Description |
|---|---|
| Scheduled | Maintenance has been planned but has not started yet |
| Ongoing | Maintenance is currently in progress |
| Completed | Maintenance has finished |
Publish an event
Select event type
In the status page management view, click Publish Event and choose either Incident or Maintenance.
Fill in event details
Configure the following fields:
| Field | Description |
|---|---|
| Title | Brief title for the event |
| Description | Detailed description of the event |
| Status | Initial status of the event |
| Affected components | Select components affected by this event and set an impact status for each |
| Responders | Assign team members involved in handling the event |
| Notify subscribers | Whether to send notifications to subscribers when publishing |
Add an initial update
Every event requires at least one timeline update. The system automatically generates an initial update record based on the information you provide.
Component impact statuses
When publishing an event, you need to specify the current service status for each affected component:- Incident impact statuses
- Maintenance impact statuses
| Status | Description |
|---|---|
| 🟢 Operational | Service is operating normally |
| 🟡 Degraded | Service is available but performance is affected |
| 🟠 Partial Outage | Some functionality is unavailable |
| 🔴 Full Outage | Service is completely unavailable |
When an event reaches a terminal status (Resolved for incidents, Completed for maintenance), all affected components must be set back to Operational.
Timeline updates
After publishing an event, you can add timeline updates to record progress and keep subscribers informed. Each timeline update can include:| Content | Description |
|---|---|
| Timestamp | The actual time this update corresponds to |
| Status change | Advance the event to its next lifecycle status (optional) |
| Description | Narrative text about the current progress |
| Component status changes | Adjust the service status of affected components (optional) |
Close an event
Updating an event to a terminal status closes it:- Incidents: Update status to Resolved
- Maintenance: Update status to Completed
Reopen an event
Closed events can be reopened. Add a new timeline update with a non-terminal status to reactivate the event.Maintenance auto-scheduling
For maintenance events, you can set a planned start time and planned end time, and enable auto-update by schedule. The system will automatically advance the maintenance status at the specified times:- When the planned start time arrives: Automatically updates status from Scheduled to Ongoing
- When the planned end time arrives: Automatically updates status from Ongoing to Completed
Manual override
Even with auto-scheduling enabled, you can manually update the maintenance status at any time:- If you manually advance the maintenance to Ongoing, the system cancels the pending auto-start task
- If you manually mark the maintenance as Completed, the system cancels the pending auto-close task
Retrospective events
When service status changes were not published in time, you can create a retrospective event to fill in historical records. Retrospective events allow you to:- Declare a past incident or maintenance
- Set precise start and end times
- Build the event timeline in actual chronological order
- Accurately associate affected components