Overview
Define the services that appear on your status dashboards.
Components are the building blocks of your status dashboards. Each one represents a service or subsystem your customers care about, with a live status indicator that reflects active incidents and maintenance.
Use the Components page to create, import, rename, and remove components. The sections below cover how status is derived, bulk import formats, and what happens when you delete a component that past events still reference.
What a component does
Components are the individual services, systems, or subsystems you want to track on your status dashboards. Each component gets its own status indicator that reflects whether that part of your infrastructure is operational, degraded, or down.
Examples of components: API, Web App, Payment Processing, CDN, Database.
A component represents one trackable piece of your platform. When you create an incident or maintenance window, you associate it with one or more components to tell your customers exactly what is affected. Informational notices can also optionally reference components — this determines which subscribers receive a notification, but does not change the component's status.
The component's current status is always derived from its active incidents and maintenance events only:
Component status
Each component shows one status label on your status dashboards. Status is derived automatically from active published incidents and maintenance affecting that component. Informational notices never change component status.
| Status type | Meaning |
|---|---|
| Operational | Reserved label when no active incident or maintenance affects this component. Not configurable — every healthy component shows Operational. |
| Configured severity | When an incident or maintenance affects the component, the label reflects the assigned severity (or the highest-severity among overlapping active events). |
Severity labels, order, colors, and icons are defined per organization. New accounts start with three default levels — for example Degraded Performance, Partial Outage, and Major Outage — but you can rename, reorder, add, or remove levels. See Severity levels for defaults and how to customize them.
StatusDashboard updates component statuses automatically when incidents and maintenances are opened or resolved. You do not manually set a component's standing status.
Creating components
- Go to Components.
- Click Add Component.
- Enter a name (required, up to 50 characters) and an optional description (up to 150 characters).
- Click Add component.
The new component immediately appears in the list with a status of Operational.
Your plan determines how many components you can create. The Components page shows how many you've used out of your plan limit.
Bulk importing components
To add many components at once, click Import components on the Components page. The dialog supports two input methods.
Paste text
Enter one component name per line. Descriptions cannot be set via paste — you can add them individually after import.
Upload CSV
Upload a .csv file (max 200 KB) with the following format:
name,description
API Gateway,REST API gateway
Payment Processing,Stripe payment service
Website,Main marketing websiteColumn reference
| Column | Required | Max length | Notes |
|---|---|---|---|
name | Yes | 50 characters | Must be unique across existing components and within the file. |
description | No | 150 characters | Omit the column or leave the value blank to import without a description. |
A header row (name,description) is detected automatically and skipped. If your file has no header row, the first data row is treated as a component. You can download a pre-formatted template from the upload dialog.
Import behaviour
Before anything is created, the dialog shows a preview that classifies each row:
| Classification | Meaning |
|---|---|
| Will create | A new component will be created. |
| Skipped | A component with this name already exists (case-insensitive match). Nothing is changed on the existing component. |
| Invalid | The row cannot be imported — name is missing, a field exceeds the character limit, or the name appears more than once in the file. |
| Quota exceeded | Your plan limit has been reached. Components beyond the limit are not imported. |
Review the preview, then click Import to commit. The results screen confirms how many components were created and details any rows that were skipped or failed.
Deleting components
Click the trash icon on a component row and confirm. Deletion is permanent.
- The component is removed from every status dashboard that included it.
- Events that referenced it are unchanged in admin. The event still stores the component's name and severity from when it was last associated.
- Public status pages only show events for components currently on each dashboard. After deletion, past events that only affected this component may no longer appear on those dashboards' history, timeline, uptime bars, or permalinks. See Dashboard scope.
- In event edit mode, a deleted component appears in a highlighted Deleted section on the Components tab. It stays checked by default, preserving the event's component association for admin and subscriber routing. Uncheck it and save to remove it from the event. If you save without unchecking, it is dropped automatically. Deleted components cannot be added to new events.
Renaming components
Click the pencil icon on a component row to change its name or description. The new name appears immediately in the components list on your status dashboards.
If an open incident, maintenance, or informational notice already references that component, you do not need to edit the event — event cards on the status dashboard and notifications sent for that event will show the current name.