Skip to main content

Component Management

Components are the building blocks of your status page. Each component represents a service or system your clients depend on, displayed with a real-time color-coded status indicator.

Component Statuses​

StatusColorMeaning
OperationalGreenService is working normally
DegradedYellowService is working but with reduced performance
Partial OutageOrangeService is disrupted for some users or some functions
Major OutageRedService is unavailable or severely impaired for most users
MaintenanceBlueService is in a scheduled maintenance window

The overall page status is the worst status of any active component.

Adding a Component​

  1. Open the status page and click the Components tab
  2. Click Add Component
  3. Fill in the form:
FieldRequiredDescription
NameYesDisplay name visible to clients — e.g., "Help Desk", "Client Portal"
DescriptionNoBrief explanation shown below the component name on the public page
StatusYesStarting status; defaults to "Operational"
GroupNoAssign to a component group (see below)
  1. Click Save

The component appears immediately on the public status page.

💡Name components from the client's perspective, not your internal system names. "Help Desk" is clearer than "ServiceDesk Pro Tickets API".

Updating Component Status Manually​

  1. Click the status badge or the edit icon on a component
  2. Select the new status
  3. Optionally add a note
  4. Save — the public page updates instantly and subscribers are notified if the status degrades

Common workflow: When a problem is identified, update the relevant component to Degraded or Major Outage before declaring an incident. This lets clients see impact at a glance without reading incident text.

Component Groups​

Groups let you organize related components under a collapsible section on the public page.

Creating a Group​

  1. In the Components tab, click Add Group
  2. Enter a Name — e.g., "Core Services", "Network", "Client-Facing Systems"
  3. Set Expanded by Default — whether the group is open or collapsed when the page loads
  4. Click Save

Assigning Components to a Group​

When creating or editing a component, select the group from the Group dropdown. Components not assigned to a group appear in the default ungrouped section.

Group Display Order​

Components within a group display in the order they were added. Drag-and-drop reordering is not currently supported; delete and recreate components to change order.

Automated Monitoring​

You can configure The One Status to automatically poll a URL and update the component status based on the HTTP response.

Configuring Monitoring​

  1. Click the configure monitoring icon (or edit the component and scroll to Monitoring)
  2. Toggle Enable Monitoring on
  3. Fill in:
FieldDescription
URLThe endpoint to poll — e.g., https://helpdesk.yourmsp.com/health
Check IntervalHow often to poll, in seconds (e.g., 60 for every minute)
TimeoutHow long to wait before marking as failed, in milliseconds (e.g., 5000 for 5 seconds)
Expected Status CodesHTTP status codes that count as "up" — e.g., [200, 204]
  1. Click Save

How Monitoring Works​

  • The system polls the configured URL every minute (minimum interval)
  • If the response matches an expected status code within the timeout, the component is marked Operational
  • If the response fails, times out, or returns an unexpected code, the component moves to Major Outage and subscribers are notified of the status change
  • When the check recovers, the component returns to Operational and subscribers are notified of the recovery
  • Uptime data is recorded and contributes to the 90-day rolling uptime percentage
ℹī¸Automated monitoring checks originate from The One Status infrastructure. Ensure the monitored URL is reachable from external IPs. Do not monitor internal-only endpoints that are not externally accessible.
💡Use lightweight health-check endpoints (/health, /ping) that return quickly. Monitoring your homepage may add unnecessary load and slower response times to your metrics.

Monitoring Status Notifications​

When automated monitoring detects a status change, subscribers receive notifications automatically — no manual incident creation required. The notification describes the component name, what the previous status was, and what the new status is.

Viewing Uptime and Response Time​

For components with monitoring enabled:

  • Uptime percentage — 90-day rolling uptime visible on the public page (if enabled in page settings) and in the Components tab
  • Response time chart — historical response time visible in the component detail view
  • Recent checks table — last N check results (timestamp, status, response time in ms, HTTP code)

See Uptime History and Performance Metrics for more details.

Deleting a Component​

Edit the component and click Delete. Deleting a component removes it from the public page immediately and removes it from the affected components list of any existing incidents.

⚠ī¸Deleting a component also removes all historical uptime and monitoring data for that component. This cannot be undone.