Status pages & boards
Public status pages and internal boards communicate component health, incidents, and maintenance to subscribers (for example email, Slack, SMS) while giving operators a single operational view.
How To: create and publish a custom status board
Step-by-step guide
Work in the Exemplar console . For example, you might name a board Production Service Board.
-
Open Status boards — From the console, go to the area where status boards / service boards are managed.
-
Start a new board — Choose Create (or equivalent) and give the board a clear name, for example by environment or audience (Production, Customer-facing, Internal ops).
-
Add rows for your stack — Attach the signals you want on one screen:
- Synthetic / endpoint monitors — HTTP(S) checks against your APIs or health URLs.
- Third-party vendors — Feeds from providers you depend on (aggregated vendor status).
- Catalog entities — Services or components from your catalog, if you link boards to catalog-backed health.
-
Group and navigate — Organize sections (for example Monitors, Third party, Catalog) so viewers can scan quickly. Use jump / in-page navigation if the UI offers it to move between sections on a long board.
-
Set the story for subscribers — Configure the global banner and legend so Operational, Downtime, Degraded, and Maintenance states read clearly. This is what stakeholders see during an incident.
-
Tie in incidents and comms — Ensure active incidents and maintenance windows surface on the board where your process expects (subscriber email, Slack, SMS, etc., per product settings).
-
Publish and share — Complete the publish flow so the board has a stable URL (public or restricted, per your setup). Share the link with teams or customers who rely on this view.
-
Smoke-check — Open the published board and confirm rows show live status, recent history bars, and that Get notified / subscription options behave as expected.
Blog
- Status pages, trust, and the limits of a green dashboard — Why public status surfaces matter; internal operational truth vs. customer narrative.
- Public status page guide for SaaS teams selling to enterprise — Enterprise expectations, SLA alignment, and checklists for security reviews and sales.