A new look for public status pages, and what 1.1.0 changes on yours
A status page now answers “is it down, and where?” before the reader scrolls. It is live on pingtower.com. A self-hosted box’s public status pages change the moment it runs 1.1.0, through the usual upgrade. If your own agents run gRPC checks, upgrade them too: see Upgrade agents that run gRPC checks.
What your readers see
- The state first. The page opens on its overall state, the components that are not operational and since when.
- Checks by region. Beside it, each region’s view of the checks your components bind, now and over the last 2 hours. Only sources named like a region appear; an agent your team named anything else stays private.
- Response times. Turn on Show response times on the page for a component to chart its checks’ last 24 hours, with now and by region.
- Groups fold. A group shows as one row with one 90-day bar of its worst component’s days, and opens by itself when something in it is wrong.
- An incident’s progress. Started, Investigating, Identified, Monitoring, Resolved, marked as it moves. The incident’s own page gives when each stage began.
It still has no JavaScript and sets no cookies on a public page. Status pages covers every part.
One thing to check: the accent
A page without an accent colour of its own used blue, #1f6feb. It now
uses violet, #7c3aed. The accent also moved: it marks the Get help
button, which is now in the header, links when they are pointed at, and the
tile that stands in for a missing logo. To keep the old blue, set the page’s
accent to #1f6feb on its Settings tab.
The badges, the embed banner and embed.json are unchanged.
Upgrade agents that run gRPC checks
If any of your own addons agents runs a grpccheck,
upgrade that agent to addons agent 0.5.0 or later. On 0.4.0 a gRPC check
can hang: the run never finishes, so the check stops reporting instead of
going down. Upgrade the tower to 1.1.0 first, then
each agent. Agents that run no gRPC check
can stay on 0.4.0; the tower still accepts them.