Add components to a status page
Add components to your Servor status page and link them to monitors so their status updates automatically — plus how to group and order them.
Components are the individual parts of your service shown on a status page — things like API, Dashboard, Database or Payments. This guide shows you how to add them and, most importantly, how to link each one to a monitor so its status updates on its own, with no manual toggling during an outage.
If you haven't created a page yet, start with Create a status page.
Add a component
Open your status page
Go to Status pages in Servor, open the page you want to edit, and find the Components section.
Add a component
Click Add component and give it a clear, user-facing name — API, Website, Email delivery. Visitors read these names, so avoid internal server names or jargon.
Link it to a monitor (recommended)
Choose the monitor that watches this part of your service. Once linked, the component's status follows the monitor's status automatically — no manual updates needed.
Save
Save the component. It appears on your public page right away, showing its current state.
Link a component to a monitor
Linking is what makes a status page maintain itself. When a component is tied to a monitor, Servor maps the monitor's status to the component:
| Monitor status | Component shows |
|---|---|
| Up | Operational |
| Degraded | Degraded performance |
| Down | Major outage |
So when a monitor detects that your API is down, the API component turns red on
the status page automatically — and returns to operational the moment the monitor
recovers. See Monitor status for how up,
degraded and down are decided.
One monitor, one component
Point each component at the monitor that best represents it. If a single service needs several checks (for example an HTTP check and an SSL certificate check), create separate monitors and separate components, or pick the check that matters most to your users.
Components without a monitor
You don't have to link every component. A component with no monitor stays on whatever status you set manually — useful for a third-party dependency you can't monitor directly, or a service you update by hand. You can also override a linked component during an incident: linking an incident to a component sets its impact for the duration and releases it when the incident resolves.
Group and order components
For larger services, group related components so the page stays readable:
- Order components by dragging them — put the things users care about most at the top.
- Group components under a heading (for example Core services and Integrations) so a long list stays scannable.
A tidy, well-ordered component list is the difference between a status page people trust at a glance and one they have to hunt through.