All docs
Monitoring & alerting
Public status pages
A status page is a public, unauthenticated page that shows your customers whether things are up, with incident history and scheduled maintenance. This page covers creating one, choosing what it reveals, adding servers and monitors, the SLA line, email subscribers and the URL it is served at.
Create a page
Open Status pages in the Monitor menu, enter a title (“CRM Stack”) and an optional URL slug (“crm”), and create it. Then open the page to configure it. You can have several pages per workspace, each with its own set of components — one per client, for example.
Overall or per-component
- •Overall only — the default. The page shows one combined status and reveals no server names. Safe to share widely.
- •Per-component — lists each server and monitor by its display name with its own status and a 30-day history bar.
Status is derived live. A server is operational when its agent is online and it has no open critical or warning alerts, degraded when it has open alerts, and down when the agent is offline. A monitor is down when its last check was down, otherwise operational. The combined status rolls up to operational, degraded, partial outage or major outage.
What goes on the page
- •Servers on this page — pick from your fleet. Only servers in your workspace can be attached.
- •Uptime monitors on this page — pick from your uptime monitors. Each monitor on the page gets a public response-time and uptime chart.
- •Description — a short welcome text under the title.
- •Branding — a logo URL and a cover image URL. Paste hosted image URLs; there is no upload.
- •Scheduled maintenance — add a window with a title, optional description, start and end. Upcoming and in-progress windows appear on the page; past ones drop off.
SLA line
If a monitor on the page has an SLA target, the public page shows its achieved availability for the current period next to the target — for example “99.97 % this month · target 99.9 %”. The target and window are set on the monitor, not on the page.
Incident history
The page lists your workspace’s incidents from the last 90 days (title, severity, status, start and resolve times) under Past incidents, and the public 30-day outage log of each component.
Subscribers
Visitors can enter an email address on the page. Opservo sends a confirmation link; only confirmed addresses are subscribed (double opt-in). Subscribers are emailed when an incident is declared and on every status change you post to it. Every email carries an unsubscribe link. Signing up twice with the same address re-sends the confirmation instead of creating a duplicate.
The URL
The page is served at https://getopservo.com/status/<slug>. Pick the slug when you create the page or change it later; a few words such as status, api, admin and config are reserved, and a slug must be unique across Opservo. If you leave it blank, Opservo generates one.
Untick Enabled to take a page down without deleting it. A disabled or deleted page returns “This status page doesn’t exist or isn’t published” to visitors and stops subscriber emails.
Last updated 2026-10-01. Found a mistake? Email hello@getopservo.com.