Skip to main content
The component is one line on the status page: “Personal Account”, “Servers in Germany”, “Subscriptions”, the visitor sees its name, current status and history in 30 days. Everything else in the Z Components is needed to get this state from where it is needed.
For whom: panel administrator, duty engineer. Required permission: statuspage.edit.

Where to start?

Start with what customers most often ask you, and call it their words: internal names like de1-inbound don’t tell the visitor anything; “Servers in Germany” say. Components fold into groups. A group is the title and the list below it, and you can fold it by default if you have dozens of servers that are the same, and a component without a group is shown as a separate line.

Where does fortune come from?

When creating a component, the first question is the source. The difference between the first two and the third is more important than it seems. The state of the nodes and the Flow knows the bar, so it sends it to the page once a minute. The page checks its service itself, from its server, and will continue to do so even when the panel is not available. For the node component, the country is inserted from the node card: a flag appears on the page next to the name. You don’t need to enter it a second time.

What to show the visitor

The display mode specifies what will appear in the component string:
  • Status – Current state only.
  • Uptime - state and share of performance in 30 days;
  • Metrics - status and schedule
  • Status and metrics — all together.
The story is drawn in 30 day divisions. The days that the incident or scheduled work occurred are clickable: the visitor opens a related event. The “Advanced” section hides the rest: show the component to visitors or not, and after how many seconds without fresh data, consider it obsolete. The outdated component is shown as “state refined,” rather than staying with the latter good value.

Own inspections

The page server performs the checks. There are five types: Each test has a set-up of interval, timeout, and stability: how many errors in a row are considered a failure, and how many successes are a recovery, and the thresholds are needed so that one lost attempt does not paint the page red.
The secret for the Authorization header is shown once, when you save it, then the bar tells you only if it’s given or not. To replace, enter a new value; to remove, clear the field.

Metrics charts

The component can show wavy graphs: latency, availability, CPU load. The series is given by a key (latency_ms, availability, cpu_percent), name and unit of measurement, collected and stored by the page itself.

Heartbeat sender

For heartbeat verification, release the sender data in the panel and immediately save the key shown and the ready command: the secret is not shown again. The new address will begin to receive data after the setting is published on runtime. Start sending more often than a given allowable interval. Before the first request, the component shows the wait; the absence of heartbeat outside the allowed interval becomes a failure. The reissue changes the sender’s data after publication; the withdrawn key no longer confirms health. Once re-released, update the sender and check for a new request. Deleting the check or revoking the key doesn’t stop an already configured external script - it needs to be disabled separately.

Verification

On the tab Overview, the component shows the current state and the completed history, and the preview on the tab ZDesign shows exactly what the visitor will see.

Restrictions

  • The number of visible components is limited by the tariff. The hidden component is not limited.
  • A component with a node or host source has to be tied to a specific panel resource, and it won’t survive without anchoring.
  • Uptime history can not be transferred from another status service: it begins from the moment the page is installed.

Typical errors

It’s been a long time. For the panel source, check that the panel is connected and that the node or Flow is alive; for your service, that the check is on and its purpose meets. The obsolescence threshold is configured there, in “Additional”.
Most often, it’s the range of codes you expect or the redirect: the default page doesn’t follow it. Also, make sure that the address is accessed from the server of the page, not just from your network.
Each validation must have a target filled: a URL for HTTP, a host and port for TCP, a name for DNS. The panel will not accept an empty target.
Related pages: Status page: review, Incidents and planned work, Processing.