> ## Documentation Index
> Fetch the complete documentation index at: https://docs.use.observer/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish your first status page

> Compose services, metrics, and SLOs into a customer-facing status page on a subdomain.

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

* A reporting metric (see
  [Define your first metric](https://docs.use.observer/docs/quickstart/first-metric.md)).
* Optionally, an SLO (see
  [Define your first SLO](https://docs.use.observer/docs/quickstart/first-slo.md)). Pages
  without SLOs render correctly but lose the rolling availability
  signal.

## 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:

```text title="example grouping" theme={null}
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**

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](https://docs.use.observer/docs/guides/custom-domain.md).

## 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](https://docs.use.observer/agent/overview.md) covers probe types, on-host
  configuration, and dashboard panels.
* [Customer-scoped pages](https://docs.use.observer/docs/guides/customer-scoped-pages.md) restrict a
  page to a named set of customers.
* [Password-protected pages](https://docs.use.observer/docs/guides/password-protected-pages.md) gate
  a page behind a shared passphrase.
* [Sign-in protected pages](https://docs.use.observer/docs/guides/sign-in-protected-pages.md) let
  people in by signing in with Google, Microsoft, or your own identity
  provider.
* [Customise the status page theme](https://docs.use.observer/docs/guides/theme-customization.md)
  applies a preset or overrides individual tokens.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.