Components
Services your team and customers already name
Service model
Components
- APIOperational
- DashboardOperational
Monitors roll up into these rows. Visibility and order follow component settings.
Problem
Generic labels do not match how you ship
When status rows do not mirror real services, teams explain context in side channels. Customers see names that do not match your architecture or docs.
Mismatched names
Hidden dependencies
Weak trust
Components give you a stable vocabulary. The same rows power internal views and the page subscribers open.
Model
What a component is
A component is a named unit of your system. Health can come from linked monitors, manual state when automation is not enough, or incident-driven updates when you wire them through.
- One row per service your customers recognize
- Description and visibility separate from internal monitor names
- Scoped to your project alongside monitors and incidents
Monitors
Link checks to the right row
Attach monitors so probe results roll into component health. You keep granular checks in the dashboard while the status page stays readable.
Status page
Control what the public sees
Toggle visibility per component, order rows for scanning, and group related services so the page matches how you communicate during incidents.
- Show or hide a component on the public page
- Groups for sections on the page
- Stable URLs and subscriber-ready structure
Components · 90-day uptime
Incident · scheduled maintenance Sat 02:00 UTC
Structure
Groups and order
Organize components into groups that render as sections on the status page. Order within a group so the most critical services appear first.
Sections
Groups become headings visitors scan before they read individual rows.
Ordering
Drag or set order so priority services lead each section.
Visibility
Hide internal-only components from the public page without removing them from the project.
Incidents
Same components when things break
Incidents can reference affected components so timelines and the status page stay aligned. Visibility rules apply whether the system is healthy or in an active incident.
Incident managementSummary
One vocabulary from probes to subscribers
Components connect monitors, incidents, and public status so every surface speaks the same language about your services.
- •Named rows that match how you ship
- •Monitors and visibility under your control
- •Groups and order for a scannable status page