Status page

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

Written for a reader who is already annoyed, so it says up or down and when it was checked, and nothing else.

Checked-seconds-ago is what makes the page believable during an outage.

Per-component rather than one overall light, because partial failure is the common case.

How it works

1
Components are checked continuously and the result published.
2
The checked-seconds-ago figure is prominent, because a status page nobody trusts is worse than none.
3
Partial failure is expressible, since one component down is the common case.
4
Written for a reader who is already annoyed, so it says up or down and nothing else.

Best for

The top of a dashboard, answering "is this going well".

Not the right choice for

Anything needing more than a glance.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

Field	Type	Filled from
Componentrequired	text	The part of the service, named as a customer experiences it.
Staterequired	text	Operational, degraded or down. Three states, because partial failure is the common case.
Uptime 30d	text	The rolling figure, which is what a contract refers to.
Checkedrequired	text	How long ago. This is what makes the page believable during an outage.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Checks are external and shallow — a component can be up and useless.
No incident history or postmortems.
No subscriber notifications.
Uptime is measured by the checks, so a gap in checking reads as uptime.

Before it works

What you have to provide, if anything.

Decide which components a customer actually experiences. Internal services on a public page are noise.
Pair with Api connectors, which is the internal view of the same failures.

In practice

A platform whose customers emailed whenever anything felt slow.

“Is it down or is it me?”

What was said to the agent

What the agent built

A status page with four components, uptime figures and a live check timestamp.

What changed

The is-it-down emails stopped. During the one real incident, the degraded payments component was the first thing anyone saw.

Better with

These do a different job on the same data. An agent can have all of them.

KPI pageLive

A few numbers genuinely drive decisions and they need to be visible without anyone running a report.

Activity logLive

Changes are made by several people or by automation, and after an incident you need to know the order of events.

API connectorsLive

The agent reaches outside itself for data or actions, and a broken credential should be visible before a customer finds it.

Who uses this page

SaaS support team

Answers from your real documentation, and escalates the rest with context attached.

IT services provider

Triages what is actually urgent, and gathers the detail before a human looks.

Utility or telecom provider

Takes meter readings and fault reports at the hour people actually notice them.

Questions

What data does the Status page page use?

It reads metric records the agent has collected. Health at a glance. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a kpi the wrong choice?

Anything needing more than a glance. It is best for: the top of a dashboard, answering "is this going well".

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.