Components (Beta)
Components let you group related monitors together on your status page and display a single roll-up status instead of individual monitor statuses. This keeps your status page clean and focused — especially when you're monitoring many services.
Beta Feature
Components are currently in Beta. Features and behavior may evolve over time.
What Are Components?
Instead of showing each monitor individually on your status page, you can group them into a Component. Each component calculates a single overall status based on the individual statuses of the monitors assigned to it.
For example, instead of showing 5 separate monitors for "Checkout Service" (web, API, database, caching, queue), you can create a "Checkout Service" component that shows a single status: Operational, Degraded, or Outage.
Component Strategies
Each component uses a strategy to determine its overall status based on the monitors inside it:
| Strategy | Behavior | Best For |
|---|---|---|
| Degraded if any monitor is down | Component shows Degraded as soon as one monitor fails | Critical services where any failure matters |
| Outage only if all monitors are down | Component shows Outage only when every monitor fails | Redundant systems where partial failures are expected |
| Degraded if majority of monitors are down | Component shows Degraded when more than half fail | Clusters and load-balanced services |
| Weighted threshold (coming soon) | Assign weights to monitors and set a threshold | Complex services with varying criticality |
Choosing a Strategy
- Use Degraded if any monitor is down for services where any single failure warrants attention
- Use Outage only if all monitors are down for services with built-in redundancy
- Use Degraded if majority down for clustered services where minority failures are expected
Strategy Examples
| Scenario | Monitors Down | Strategy | Result |
|---|---|---|---|
| Web + API both monitored | 1 of 2 | Any Down | Degraded |
| Web + API both monitored | 1 of 2 | All Down | Operational |
| Web + API both monitored | 2 of 2 | Any Down | Outage |
| 3-node cluster | 2 of 3 | Majority Down | Degraded |
| 3-node cluster | 1 of 3 | Majority Down | Operational |
Display Order
Each component has a Display Order value that controls where it appears on your status page:
- Lower numbers appear first (at the top)
- Higher numbers appear later (further down)
Use display order to prioritize your most critical services at the top of the page.
Hide Monitors Toggle
When enabled, the Hide monitors toggle hides all individual monitors within a component from the status page. Only the component's roll-up status is shown.
This is useful when: - You want a clean, simplified view for external users - Individual monitor details might confuse non-technical visitors - You have many monitors for a single service
When disabled, both the component status and the individual monitor statuses are visible.
Creating a Component
- Navigate to the Components section from the monitor menu (labeled "Components [Beta]" in the sidebar)
- Click Create Component
- Enter a name for your component
- Select the monitors to include
- Choose a strategy
- Set the display order
- Toggle "Hide monitors" if desired
Once created, the component can be selected when creating a status page instead of picking individual monitors.
Managing Components
- Edit: Change the name, strategy, display order, or monitor assignments at any time
- Delete: Remove a component when it's no longer needed (monitors are not affected)
- Reorder: Adjust display order values to change the rendering sequence on the status page
Need Help?
If you need assistance with components, reach out using the "Need Help?" button on the bottom right corner or email us at support@uptimeobserver.com.