Skip to main content
Status pages use components to represent individual services or functional modules, and sections to group related components for a clearer structure. This guide covers how to manage components and sections.

Components

Components are the basic units of a status page. Each component represents a specific service or feature. Events reflect actual service status through their impact on components.

Create a component

Add a new component in the status page Component Management section with the following fields:
FieldRequiredDescription
NameYesDisplay name for the component; must be unique within the status page
DescriptionNoBrief description of the component
SectionNoAssign the component to a section
OrderNoControls the display order on the status page
Newly created components begin tracking uptime from the moment of creation. If you need to start tracking from an earlier point in time, you can customize the available-since timestamp.

Edit a component

You can modify a component’s name, description, section assignment, and order at any time. When changing the name, ensure it does not conflict with other components on the same status page.

Delete a component

Deleting a component removes its uptime data and related subscriptions. Impact records in already-published events that reference this component are not affected.

Component visibility

Components support two visibility options:
OptionEffect
Hide uptimeThe component is displayed on the status page but uptime statistics are hidden
Hide allThe component is not displayed on the status page and is excluded from uptime calculations
For internal-only service components that you do not want to expose to status page visitors, use the “Hide all” option. Hidden components can still be referenced in events.

Sections

Sections group related components together for a clearer status page structure. For example, you can group “Web App”, “API Service”, and “Database” under a “Core Services” section.

Create a section

Add a new section in the status page Section Management area with the following fields:
FieldRequiredDescription
NameYesDisplay name for the section; must be unique within the status page
DescriptionNoBrief description of the section
OrderNoControls the display order on the status page

Edit a section

You can modify a section’s name, description, and order at any time.

Delete a section

Deleting a section does not delete its components. Instead, the components become ungrouped and continue to be displayed independently on the status page.

Section visibility

Like components, sections also support visibility controls:
OptionEffect
Hide uptimeThe section is displayed on the status page but uptime statistics are hidden
Hide allThe section and all its components are hidden from the status page and excluded from uptime calculations
Setting a section to “Hide all” also hides all components within it, even if those components are not individually set to hidden.

Organization tips

1

Define components by business function

Create one component for each user-facing service or functional module, such as “Web Console”, “API Gateway”, or “Billing System”.
2

Create sections by service tier

Group components by service tier or business domain, such as “Core Services”, “Monitoring & Alerting”, or “Third-party Integrations”.
3

Use visibility controls wisely

For internal dependencies or backend infrastructure components, use hidden options to keep the status page clean.