Components - Statux Pages Help

Components represent the individual services and systems displayed on your status pages. Track their health, organize them into groups, and automate status updates.

What Are Components?

Components are the building blocks of your status page. Each component represents a distinct service, system, or piece of infrastructure that your users care about. When visitors view your status page, they see a list of components along with each one's current operational status.

Common examples of components include:

API Server
Web Application
Database
CDN / Static Assets
Authentication Service
Payment Processing
Email Delivery

Component Status Levels

Every component has one of five status levels at any given time. These statuses are displayed on your public status page with color-coded indicators so visitors can quickly assess the health of each service.

Operational — The component is functioning normally. This is the default status for new components. Displayed with a green indicator.
Degraded Performance — The component is working but experiencing slowness, elevated error rates, or reduced capacity. Displayed with a yellow indicator.
Partial Outage — Some functionality of the component is unavailable. For example, writes may be failing while reads still work. Displayed with an orange indicator.
Major Outage — The component is completely unavailable or non-functional. Displayed with a red indicator.
Under Maintenance — The component is offline for planned maintenance. This status is typically set automatically when a scheduled maintenance window begins. Displayed with a blue indicator.

Note: The overall status displayed at the top of your status page is derived from the worst status among all components. If one component has a Major Outage, the page-level status reflects that.

Creating Components

To add a new component to your organization:

Navigate to Components in the sidebar.
Click Add Component.
Enter a name for the component (this is displayed on the public status page).
Optionally add a description to provide additional context about what this component covers.
Select one or more status pages that this component should appear on.
The component is created with an initial status of Operational.

Custom Components

All components you create are custom components that you fully control. You define the name, description, status page associations, and can update the status at any time through the dashboard, API, or webhook.

Third-Party Components

In addition to your own services, you can add third-party components to your status page. These represent external services that your product depends on (for example, AWS, Stripe, Twilio). Third-party components let your visitors see whether an issue they are experiencing might be caused by an upstream provider.

To add a third-party component:

Click Add Component and select the Third Party option.
Search for the external service from the available list.
Select which of their components you want to track.
The third-party component status is updated automatically based on the provider's status feed.

Component Groups

Component groups let you organize related components under a collapsible heading on your status page. For example, you might group all database-related components under a “Data Layer” heading, or all regional endpoints under “API Regions.”

Creating a Group

In the Components view, click Add Group.
Enter a name for the group.
Drag existing components into the group, or create new components directly inside it.

Renaming a Group

Click the group name or the edit icon next to it to rename the group. The new name is immediately reflected on your public status page.

Deleting a Group

When you delete a component group, the components inside it are not deleted. They are moved out of the group and become ungrouped components on the status page.

Reordering Groups

Drag and drop groups to change the order they appear on your status page. The order in the dashboard matches the order visitors see.

Drag-and-Drop Reordering

Components and component groups can be reordered using drag and drop in the dashboard. The display order on your public status page matches the order in the dashboard.

Click and hold the drag handle (the six-dot icon) on a component or group.
Drag it to the desired position.
Release to drop it in place.
You can drag components into or out of groups.
The new order is saved automatically.

Tip: Place your most critical or most-visited components at the top of the list so they are the first thing visitors see.

Updating Component Status

There are four ways to update a component's status:

1. Manually (Dashboard)

Click on any component in the Components view to open its detail panel. Use the status dropdown to select the new status. The change is reflected on your public status page immediately.

2. Via the API

Use the Statux Pages API to programmatically update component status. This is useful for integrating status updates into your deployment pipelines, runbooks, or custom tooling. See the API Documentation for endpoint details.

3. Via Monitoring Integrations

Connect monitoring tools like New Relic or Datadog to automatically update component status when a monitor triggers an alert. When the monitor recovers, the component status is automatically restored. See the Monitoring section in the dashboard sidebar for setup instructions.

4. Via Component Webhooks

Each component can have its own unique webhook URL. External systems send HTTP POST requests to this URL to update the component's status. This is the most flexible option for custom integrations. See the next section for details.

Component Webhook Tokens

Component webhooks provide a simple, token-based mechanism for external systems to update a component's status without needing full API authentication.

Generating a Webhook Token

Click on a component to open its detail panel.
Scroll to the Webhook section.
Click Generate Token.
Copy the webhook URL and token. The token is shown only once — store it securely.

Using the Webhook

Send an HTTP POST request to the webhook URL with the desired status in the request body. The webhook validates the token and updates the component status accordingly.

Example use cases:

A CI/CD pipeline sets a component to “Under Maintenance” before a deployment and back to “Operational” after.
A health-check script sets a component to “Major Outage” when consecutive failures are detected.
A third-party monitoring tool sends status updates via webhook when it detects degraded performance.

Security: Treat webhook tokens like passwords. Do not expose them in client-side code, public repositories, or logs. If a token is compromised, regenerate it immediately from the component detail panel.

Linking Components to Multiple Pages

A single component can appear on multiple status pages. This is useful when a shared service (like a database or authentication system) is relevant to more than one status page.

To link a component to additional pages:

Edit the component.
In the Status Pages section, check the additional pages you want this component to appear on.
Save your changes.

The component status is always the same across all pages it is linked to. Updating the status once updates it everywhere.

Unlinking a Component

To remove a component from a status page without deleting it:

Edit the component.
Uncheck the status page you want to remove it from.
Save your changes.

The component remains in your organization and on any other pages it is linked to. It is simply no longer visible on the unlinked page.