Skip to content
StatusOwlDocs

Services on your page

Attach monitors to a status page as components, control order and visibility, and understand how the page-level rollup is calculated.

Last updated

A component is one row on your status page — "API", "Web", "Auth", "Background workers". Visitors see a per-component health row; you control which monitor backs each one, what order they appear in, and whether they are shown publicly.

This page covers the lifecycle: attach, reorder, hide, detach. For reporting against a component, see Incidents.

What a component is

In StatusOwl a component is a monitor attached to a status page. There is no separate component object to create. A component is a view of an existing monitor plus two per-page settings: display order and visibility.

Renaming the monitor renames the component everywhere it appears. The monitor's description is shown alongside it. Every component is backed by exactly one monitor, and its public status mirrors that monitor's last result.

Component groups do not exist

Other status page tools let you nest components under a parent ("API → Auth, Search, Webhooks"). StatusOwl renders a flat list. If you need the appearance of grouping, order related components together and name them consistently — "API · Auth", "API · Search".

Attaching a monitor

  1. Open the status page and find the Components card.
  2. Click Add Component and pick a monitor from your organization.
  3. The monitor is added to the bottom of the list, visible by default.

A monitor can be attached to several pages at once; attaching it to one does not detach it from another. The component immediately reflects the monitor's most recent result — you do not need to wait for the next check.

Display order

Components render in the order set on each page. Drag a component to reorder, or use the per-row Move up / Move down controls. Order is stored on the page-to-monitor link, so two pages sharing the same monitor can order it differently.

A useful default: order by what the visitor recognises. Front door first (marketing site, login), then the things behind it. People form an impression from the top of the page.

Hiding a component

Each component has a per-page visibility toggle. A hidden component is not rendered publicly but stays attached and keeps receiving data. Useful while you are settling a new monitor in, or when a noisy internal probe would confuse people mid-incident.

Hidden is not deleted. Flip the toggle to show it again.

Per-component metadata

Label, description and current status all come from the underlying monitor. To change any of them, edit the monitor — the change appears on every page it is attached to.

There are no per-component icons and no link-out URLs. Use a descriptive monitor name as the visible label.

Page rollup

Monitors have a binary status: up or down. The page turns those into the summary a visitor sees:

  • Operational — every visible component is up.
  • Degraded — at least one visible component is down.
  • Unknown — no recent data, or nothing attached yet.

There is no "partial outage" or "major outage" tier on the rollup itself. To communicate severity, open an incident with an impact of minor, major or critical; the incident banner sits above the component list and the banner takes its colour from the impact.

Banner priority, when more than one thing is true at once:

  1. Maintenance that is in progress.
  2. The highest-impact active incident.
  3. An automatically-detected outage with no incident declared.
A component follows its monitor exactly

If a monitor goes down at 14:03 and recovers at 14:04, the component flickers down → up and the rollup briefly reads Degraded. Nothing smooths that. What filters transient blips out of your incident history is the three-consecutive-failure threshold — a single blip never opens an incident.

Detaching a component

Detaching removes the row from the page. The monitor and all its history stay intact, and other pages using the same monitor are unaffected.

  1. Open the Components card.
  2. Click the ⋯ menu next to the component → Remove.
  3. Confirm.

To delete the monitor itself along with its history, do that from the Monitors page. Detaching here only severs the link.

Practical advice

  • One component per service your customers can name. If they would not recognise the name, hide it or leave it off.
  • Order from the visitor's point of view, not your architecture diagram.
  • Attach hidden while you settle a new monitor, watch a few intervals, then unhide.

See also