Service status & outages¶
The Service Status page (Operations → Service Status) lets you set the status of each service directly and leads to its outage history. Admins and service managers see all active services, service owners only their own. If a service owner is not responsible for any service, the page shows "You are not responsible for any services yet.".
Setting a status¶
- Open Operations → Service Status.
- Choose a new status for the service.
- Optional: for a disruption, when incidents are open, the selection Attach to open incident appears. If you choose an incident, the status is recorded at the incident's occurred time. "— don't attach —" sets the status without a link.
- Click Set. The change appears on the public page immediately, and notifications are sent according to the templates and mute settings.
Statuses:
| Status | When to use |
|---|---|
| Operational | Everything works. Ends all open outages of the service. |
| Degraded Performance | Works, but slower or with reduced functionality |
| Partial Outage | Some functions or users are affected |
| Major Outage | The service is unavailable |
| Under Maintenance | Unplanned maintenance without a maintenance window |
For planned work, a maintenance window is the better choice. It sets under_maintenance automatically for the planned period and notifies subscribers.
Each row also has a Create incident link that opens the incident form with this service. The form opens for admins, service managers and service owners; service owners see the link only for their own services. A colored icon shows the result of the last uptime check.
Only services in the mode Active (Public) or Active (Internal) appear in the list.
Outage history¶
Click a service to see its Outage history. Each entry is an outage window with status, start and end, with a link to the related incident where there is one. All roles can view it. Admins, service managers and SLA managers can change it for all services, service owners for their own. Without permission, the page shows "You can view these outages, but only users with access for this service can edit or delete them.".
Each row is a form with start, end, status and Save:
- Correct times: start and end are entered in the time zone of the settings. An empty end means the outage is still running. If the window overlaps a neighbor, it is adjusted: the start is never before the end of the previous outage, and the end never after the start of the next one.
- Change the severity: choose a status and save. The status Operational removes the entry from the history, for example for a false alarm.
- Delete an outage: removes the window after a confirmation ("Are you sure? Deleting this outage also removes the link to its incident, if any."). Deleting does not reverse a status that is already set on the service, so check the current status afterwards.
Warning
Corrections are reflected in uptime and SLA figures immediately. An outage that is confirmed in an SLA report is locked: the form is disabled and there is no delete button. On the server, editing and deleting are refused with "This outage is confirmed in an SLA report and cannot be edited." or "… cannot be deleted.". While a report is running in which the outage still needs confirmation, a Confirm button appears in the row. See SLA management.
Automatic status from uptime checks¶
If a service has an uptime check, its status can be set automatically after a series of failed checks. In that case, the checker records that it set the status. A manual change overrides the automatic status, and the checker will not restore a status it did not set. See Uptime checks.
Status through the API¶
Monitoring tools can set and end outages through the API with a token. Entries created this way appear in the history like manual ones. See Public API.