The team view of a status page

Your status page is written for your customers. It answers one question — is something broken — and it deliberately answers nothing else.

The team view is the same page written for the people fixing it. It lives inside InfraNest, behind your normal sign-in, and it shows two things your customers never see: who is on call, and where the runbook is.

Go to Status Pages and click the lifebuoy icon on any page.

#What you see

The strip at the top — overall status, how many of the page's services are up, the average uptime over the last 30 days, and when the next maintenance window starts.

On call — whoever is holding the pager for this page. You write this yourself; see below.

Open right now — every incident currently running on this page's services, with a link to the public write-up. That link is the one to paste into a support ticket: it is the page your customer can read.

Services, last 30 days — every service on the page, grouped exactly as your customers see them grouped, with its uptime bars, when it was last checked, and how many monitoring regions are still reporting on it. If a service has a runbook link, there is a Runbook button beside it.

The page refreshes itself every 30 seconds, so you can leave it open during an incident.

#Set the on-call contact

Go to Status Pages, open the page, and fill in On-call contact.

It is free text, so put whatever your team actually needs: a name and a phone number, a link to your rota in PagerDuty or a spreadsheet, or a Slack channel. There is no rota built in — this is a pointer to wherever yours already lives.

Clearing the box removes it. Worth doing when someone leaves the rotation: a stale name here is how last quarter's on-call keeps getting called.

#Add a runbook link to a service

In the same place, open the Components tab, click a service, and fill in Runbook link.

It has to start with https://. Point it at the document for that service, not at your wiki's front page — the whole reason it sits on the service is that someone woken at 3am should land on the right document, not on an index.

#Who can see it

Only people signed in to your workspace.

This is worth being precise about, because status pages have a password option and the two are unrelated. Someone who knows your status page's password sees the public page and nothing more. The on-call contact and the runbook links are not sent to that page at all — they are only ever sent to the team view, and the team view asks for a real sign-in.

#Which plans include it

The team view is part of private status pages. If your plan does not include it, the page tells you so and everything else about your status page works exactly as before.