Skip to main content
Status pages are the customer-facing surface of the resources configured in the previous two quickstart pages: services, metrics, SLOs, and incident updates. This page covers creating a page, showing content sections, and shipping it on a subdomain.

​
Prerequisites

​
Steps

1

Create the page

In the console, open Status pages, then New status page. Configure:
  • Title: the heading rendered at the top of the page.
  • Subdomain: the page is served at <subdomain>.use.observer. Lowercase letters, digits, and hyphens are accepted. Some first-party names (for example www, app, admin, blog) are reserved.
  • Layout: pick a layout; theme is set in the builder (the form also accepts an accent color).
Save the page. It is now reachable but shows no metrics yet.
2

Add metrics

Open the page in the builder. Add the metric defined earlier in the Metrics panel and make sure the Individual metrics section is visible.Metrics can be grouped by namespace to mirror service topology:
example grouping
Each group’s name renders as a section heading on the published page, and the metrics within share a status row.
3

Add the SLO strip

Make sure the SLO strip section is visible. The strip renders the target, the window, the remaining error budget, and the current burn event.The strip requires the SLO’s Show on public status page setting to be on. If the strip does not render after publish, open the SLO and turn that setting on.
4

Publish updates and incidents (optional)

The Incidents section surfaces incident posts. In the console, open Incidents, then New incident, and pick this page’s services (or the page itself under Show on pages). Once published, the page renders the incident with its timeline and follow-up posts. Updates are not required to publish the page; this step shows where they appear when an incident is in progress.
5

Visit the page

<subdomain>.use.observer serves the rendered page. To use your own hostname, see Custom domains.

​
Result

The page renders a header with the rolled-up status and any active SLOs, followed by a section per metric group, followed by an incident timeline. Every value reflects live metric data computed against the configured thresholds and SLO targets.

​
Next