Everyone

Status Components

Define the services or infrastructure components that appear on your status page.

Last updated 1776211200

What Are Components?

Components are the individual services or infrastructure items listed on your status page. Each component has a name, a current status, and optionally belongs to a component group. Clients see each component's status at a glance on /status.

Example components for a hosting company:

  • Shared Hosting
  • VPS Hosting
  • Email (Inbound / Outbound)
  • DNS
  • Client Portal
  • Billing System
  • Control Panel

Creating a Component

  1. Go to Admin → Content → Status → Components.
  2. Click Add Component.
  3. Fill in the fields.
  4. Click Save.

The component appears on /status immediately.

Component Fields

Field Required Notes
Name Yes Displayed publicly on the status page
Description No Short clarifying text shown below the name
Group No Assign to a component group for organised display
Sort Order Yes Controls order within the group or overall list
Status Yes Current operational status (see below)
Public Yes Toggle off to hide from portal but keep for internal tracking

Component Statuses

Status Colour Meaning
Operational Green Fully functioning as expected
Degraded Performance Yellow Functioning but slower or intermittently impaired
Partial Outage Orange Some users or regions affected
Major Outage Red Service is down or unusable for most users
Under Maintenance Blue Intentionally offline for planned maintenance

Update a component's status by editing the component record or from within an active incident (updating an incident can optionally change the component status in the same action).

[!IMPORTANT] Set affected components back to Operational as soon as an issue is resolved. Leaving a component in a non-Operational state when the service has recovered causes the overall status header to remain red/amber and erodes client trust.

Component Groups

Component groups let you cluster related components under a labelled heading on the status page. For example:

  • Core Services — Shared Hosting, VPS, Reseller Hosting
  • Communication — Email, DNS
  • Management — Client Portal, Control Panel, API

To create a group:

  1. Go to Admin → Content → Status → Component Groups.
  2. Add a group name and sort order.
  3. When creating or editing components, assign them to the group.

Public vs Admin-Only Components

Setting Public to off hides a component from the /status page but keeps it in the admin panel. Use this for internal infrastructure components (database servers, internal monitoring systems) that you want to track but not expose to clients.

Admin-only components still factor into internal dashboards but do not affect the publicly calculated overall status header.

Updating a Component's Status Directly

To update a component's status outside the context of an incident:

  1. Edit the component record.
  2. Change the Status field.
  3. Save.

For ongoing issues, it is better to create an incident and update the status via the incident workflow — this creates a timestamped log that clients can read.