Components

Put things on your status page that Hyperping does not monitor, and set their status by hand.

Most services on a status page are backed by a monitor: Hyperping checks them and the status updates itself. A component is the other kind. It appears on your page like any other service, but nothing checks it, so its status only changes when you publish an incident or a maintenance window that affects it.

Components exist for everything you are accountable for but cannot ping:

• A third-party service your product depends on, like a payment provider or an email sender
• Something with no public endpoint: a data pipeline, a batch job, an internal queue
• A physical or human dependency, like an office network or a support desk
• A service you want listed on the page before its monitor exists

Create a component

1. Open Components

   Go to Components in the sidebar, under Status Pages.

2. Create it

   Hit New component and give it the name your visitors should see, for example "Payment provider" or "Email delivery".

3. Add it to a status page

   Open your status page and add the component the same way you add a service. One component can sit on several status pages, and the Components list shows which pages each one appears on.

Changing a component's status

A component sits at operational until you say otherwise. To change that, publish an incident or a maintenance window and select the component as an affected service. Its status on the page follows the incident, and returns to operational when you resolve it.

That is the whole model: there is no separate status dropdown to forget about, and no way for a component to be stuck red with no incident explaining why.

What components do not have

Because nothing checks them, components carry no uptime percentage, no response time chart, and no 90-day history bar. On the page they show their current status and the incidents that touched them, nothing more. A page mixing monitored services and components will show uptime for some rows and not others, which is expected.

Troubleshooting

Next steps