A component is one line on the status page, such as a node, a server or your website. They are managed in Admin > Status Page > Components.
Nodes appear on their own
Every node of the panel is added automatically, and each one is checked every minute. You do not have to create them. A node whose servers are not on the page is still checked, because the customers' Uptime tab needs that data.
Types
| Type | What it checks |
|---|---|
| Node | Whether the node's Wings answers. It also reads the state of every server on the node. |
| Server | Whether a server is running, from the node's answer. Optionally shows the players online of a Minecraft Java server. |
| Website (HTTP) | Fetches a URL and compares the status code with the one you expect. |
| TCP port | Opens a connection to a host and port. |
| Minecraft server | Asks a Minecraft Java server for its status: whether it can be joined, the players online and the version. |
Node and Server components need no network access of their own. They use the answer Wings already gives the panel.
Adding a component
Press Add component and fill in:
- Type, and then the node or server to watch, or the URL, or the host and port.
- Public name: what visitors see on the status page.
- Group: components with the same group are shown together under one heading, for example a location such as "Frankfurt".
- Expected status code (Website): the code a healthy site returns.
- Show players online (Server and Minecraft): displays the player count and version.
- Show on the public page: turn it off to keep monitoring a component without showing it.
- Monitor it: turn it off to pause the checks.
Organizing
Use the arrows to move components up and down. The order and the groups you set are the order and the groups visitors see. The list lets you switch Show on the public page per component without opening it.
Statuses
| Status | Meaning |
|---|---|
| Operational | Answers normally. |
| Degraded | Answers, but slower than the slow answer threshold. |
| Down | Failed the configured number of checks in a row. |
| Maintenance | Inside a maintenance window. |
| Offline | A server that is stopped or suspended. This is not counted as an outage. |
| Unknown | No data yet. |
The banner at the top of the page summarizes all of them: all systems operational, degraded, partial outage (less than half of the components down), major outage (half or more down) or maintenance.
How a component goes down and up
Checks run every minute. A component is marked down after N failures in a row (3 by default) and up again after M successes in a row (2 by default). Both numbers are in Settings. This keeps one lost packet from opening an incident.
Checking external targets safely
Website and TCP checks refuse private and reserved addresses by default, so they cannot be used to probe your internal network. If you really monitor an internal service, turn on Allow private addresses as targets in Settings.
Previous: Installation · Next: Incidents and Maintenance