Components and sections

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:

​

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:

---

​

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:

​

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:

---

​

Organization tips