Publish your first status page

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, adding content blocks, and shipping it on a subdomain.

Prerequisites

• A reporting metric (see Define your first metric).
• Optionally, an SLO (see Define your first SLO). Pages without SLOs render correctly but lose the rolling availability signal.

Steps

1. •

   Create the page

   In the console, open Pages, then New page. Configure:

   • Title: the heading rendered at the top of the page.
   • Subdomain: the URL path, served as <subdomain>.<your-cloud-host>. Lowercase letters, digits, and hyphens are accepted. The values admin and blog are reserved.
   • Theme: pick a preset; further customization is available in the page builder.

   Save the page. It is now reachable but contains no content blocks.

2. •

   Add metric blocks

   Open the page in the builder. Drag the Metrics block onto the canvas and select the metric defined earlier.

   Metrics can be grouped by namespace to mirror service topology:

   api/
     checkout-api
     payment-router
   web/
     dashboard

   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

   Drag the SLO strip block. Select the SLO. The strip renders the target, the window, the remaining error budget, and the current burn event.

   The block requires the SLO's Public flag to be enabled. If the strip does not render after publish, open the SLO and toggle public visibility on.

4. •

   Publish updates and incidents (optional)

   The Updates block surfaces incident posts at the top of the page. Open the page's update feed, create an Update with type Incident, and 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>.<your-cloud-host> resolves to the rendered page. On a local development cloud the URL is http://<subdomain>.localhost:3000. In production it follows the wildcard DNS the operator has pointed at the cloud.

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

• Observer Agent reference covers probe types, on-host configuration, and dashboard panels.
• Guides on customer-scoped pages, password protection, and theme customization will appear in the sidebar as content is published.