Skip to main content

Status Pages

A status page is a public page where your users can see the current health of your services, follow active incidents in real time, read past incident history, and subscribe to email updates. It's the page you link to from your app, docs, or support channels when something is (or isn't) happening.

Autoheal status pages are modeled after the pattern your users already know from Atlassian Statuspage: a page lists services, incidents describe what's happening and which services are affected, and each service shows an at-a-glance status.

The pieces​

  • Status page — one public page (e.g. "Acme US"). A tenant can have several (e.g. one per region or product). Each page has its own public web address.
  • Services — the components you show on the page (e.g. API, Dashboard, Webhooks). Each has a status: Operational, Degraded performance, Partial outage, Major outage, or Under maintenance.
  • Incidents — a post with a lifecycle (Investigating → Identified → Monitoring → Resolved) and a running timeline of updates. An incident says which services it affects and how badly; the affected services' status updates automatically.
  • Updates — a free-form single-message post for anything that isn't a lifecycle incident: a heads-up, a scheduled-maintenance note, or a general announcement. It has no status and doesn't change service health.
  • Subscribers — end users who opt in (double opt-in by email) to be notified when you publish or update a post.

How service status is decided​

You don't set a service's overall status by hand. Autoheal derives it from your open incidents: a service shows the worst impact among all unresolved incidents that list it. When you resolve the last incident affecting a service, it returns to Operational automatically.

Public vs. private​

Every page has a single visibility switch:

  • Private (default) — the page exists and you can build it out, but it is not served publicly.
  • Public — the page is live at its web address for anyone to see.

Flipping a page to Public is how you "publish" it. Posts you create are live the moment you create them — there is no separate draft step — so a private page lets you set everything up before anyone can see it.

You can also serve a public page on your own subdomain (e.g. status.yourcompany.com) instead of the default address — see Use your own domain.

What your users see​

A published page shows two sections:

  • Active incidents — unresolved incidents, with their latest updates.
  • Recent updates — resolved incidents and update posts from the last 15 days, newest first.

Visitors can also subscribe by email to get notified of new and updated posts.

Next steps​