Services & groups¶
A service is what the status page shows: an API, a website, a database, and so on. Services are organized in groups, which appear as cards on the public page.
Only admins and service managers can open these areas. Other roles are redirected to the dashboard. Service owners see their services under Service Status.
Service groups¶
Open Services → Service Groups, or click Manage groups on the Services page.
- Create: enter a name and click Create group. Group names must be unique across the system ("A group with this name already exists.").
- Rename: change the name in the list and click Save.
- Delete: only possible when the group contains no services. Otherwise Delete is disabled, and its tooltip shows the number of services.
Warning
Services can neither be moved to another group nor deleted in the UI. A group that contains services therefore stays. Set services you no longer need to the mode Inactive or Archived.
Services¶
The Services page shows one table per group with the columns Name, Description, Mode and Notifications (On/Off). Use New service to create a service.
Creating a service¶
| Field | Effect |
|---|---|
| Group | Determines the card on the status page. Cannot be changed later. |
| Name | Shown on the public page. 2 to 100 characters, unique within its group ("A component with this name already exists in this group."). |
| Description (optional) | At most 500 characters. Shown on the service detail page. |
| Service mode | Lifecycle of the service, see below. Default: Active (Public). |
| Responsible user | The owner. This user may set the status and maintain the outages of the service. |
Create service creates the service.
Editing a service¶
The page Edit service — (name) is split into cards. Save each card separately.
| Card | Fields |
|---|---|
| Basic info | Name, Description and Notes: internal notes for your team, at most 5000 characters, never shown publicly |
| Status & ownership | Mode, Responsible (responsible user), Business owner (informational only, gives no rights) and SLA relevant |
| Notifications | Send notifications for this service (master switch), Notify via with Send Mail, SMS, Webhook and Push, Additional notification email address with Set |
| Uptime check | Automatic uptime check with a View history link. See Uptime checks. |
SLA relevant: if set to "no", the service is left out of SLA reports and their exports, and its outages need no confirmation. It stays on the SLA page and can still be assigned plans and targets. See SLA management.
Targets, schedule and incident SLA metrics of a service are not set here, but under SLA-Management → SLA.
Service mode¶
| Mode | Meaning |
|---|---|
| Draft | Being prepared, not shown publicly |
| Active (Public) | Shown on the public page |
| Active (Internal) | Shown on the status page only to signed-in team members |
| Inactive | No longer in service |
| Archived | Only visible here and can no longer be renamed. Missing from the dashboard and the outage history. |
Setting the status and creating incidents and maintenance is only possible for Active (Public) and Active (Internal).
Practical advice¶
- Use one service per thing a customer can notice. An internal database is usually not a separate service unless customers feel its outage.
- Assign a responsible user to every service. Without an owner, only admins and service managers can act on it.
- Turn off Send notifications for this service temporarily during planned work. Remember to turn it back on.
- Check the uptime history of a service before you change its SLA target. Changing a target affects future calculations only, not confirmed reports.