Public Status Pages¶
Preview feature
Status Pages are off by default — menu item, page and API (including the public pages) are blocked until a super admin enables the area under Admin → System → Preview features. The area is not yet stable.
A status page is the publicly accessible "are our services up?" page. Vesana can create one or more per tenant, each under its own slug.
Concept¶
flowchart LR
OS[Vesana data] --> SP[Status page]
SP --> URL["/status/<slug>"]
URL --> KU[End customer / staff]
The status page is read-only — only curated statuses are shown. No login required (optionally password-protected).
Status pages are included in every edition, also without a license key.
Creating a status page¶
/status-pages → New Status Page:
| Field | Meaning |
|---|---|
| Title | "Acme Production Status" |
| Slug (URL path) | address of the page: /status/<slug> |
| Tenant | source tenant — only asked if you see several tenants (super admins: default is the first active tenant) |
| Primary Color | accent colour of the page (default green) |
| Timezone | pre-filled with the instance timezone, otherwise UTC. Must be a valid IANA name (for example Europe/Berlin). The day boundaries of the 90-day bars and the outage minutes follow it |
The page's Settings tab adds title, description, primary colour, Publicly accessible and Password Protection. A page that is not publicly accessible answers "not found" for everyone — there is no logged-in access to it.
Components = hosts¶
Whole hosts are added to a status page as components (Add Hosts, with a tenant filter). Per host:
| Field | Meaning |
|---|---|
| Displayed Services | by default all active checks of the host feed into the shown status — optionally limit to a subset (e.g. show only the HTTP check, hide the internal CPU check) |
Every host shows a 90-day uptime bar. There is no free display grouping ("Web", "API", …), no display-name override per component and no way to change the order in the interface. Deleted or disabled hosts and checks do not appear on the public page.
A check only counts as disrupted on the page once it actually alerts — short spikes that have not triggered an alert yet stay "Operational".
Password protection¶
A status page can optionally be locked with a password (Settings → Password Protection tab, also "Random password"). Visitors enter it once on the page; access then lasts 24 hours in that browser tab. Subscribing also requires the password. After a password change old access is invalid immediately.
Send access via email sets the entered (or a random) password for the page and sends the link together with the password to a stakeholder address. Without a configured SMTP server Vesana reports the failure.
Content¶
The page shows:
- current status per host component
- ongoing incidents with an update timeline and resolved incidents of the last 14 days
- scheduled and ongoing maintenance
- 90-day uptime per host
- email subscription for notifications
Incidents¶
Some incidents cannot be detected automatically (third-party outage, pure communication update). Create one via Create Incident with title, status (investigating/identified/monitoring/resolved), impact (minor, major or critical) and optionally affected hosts.
Updates can be added to an incident — the page shows a timeline of status + text per update. Mark as resolved closes the incident (with an optional resolution note).
Planned maintenance¶
Maintenance is created directly on the status page (Maintenance → Plan Maintenance tab, with title, description, affected hosts, start and end) — it is a category of its own, not an automatic copy of internal downtimes. Vesana switches it from "Scheduled" to "In Progress" and "Completed" by itself; "Complete Maintenance" ends it early.
Subscriptions¶
End customers can sign up by email on the page, with double opt-in confirmation by mail. Selectable: critical outages, degraded performance, recovery notifications. Only confirmed subscribers receive mail; unsubscribing works via the personal link in every mail. An old subscription link of a deleted or private page no longer works. The admin sees the subscriber list on the page and can remove entries.
Privacy¶
The status page only shows what was added as a component — measurements of other checks stay invisible. Note: for each host the page also delivers its hostname, even if a display name is set.
Permissions¶
Status pages use the dashboard permissions:
| Permission | Effect |
|---|---|
dashboards.view |
see status pages in management |
dashboards.edit |
create, edit, hosts, incidents, maintenance, password, access mail, delete |
There are no dedicated status_page.* permissions.