Status Pages
Status pages let you communicate service health to your users through a branded, public-facing page. Instead of fielding "is it down?" messages during an outage, point users to your status page where they can see real-time information and subscribe to updates.
What a status page shows
- Overall status -- A summary indicator showing whether all services are operational, some are degraded, or there is an active outage.
- Per-monitor status -- Each monitor you assign to the page shows its current state (operational, degraded, or down). A system is shown as down only once Sentro has confirmed it is down, so a single request lost in transit never turns a customer-facing page red.
- Uptime history -- One bar per day over the configured history window (e.g., 90 days). The bars are history, not current state: a monitor that was down earlier today shows a coloured bar for today even after it recovers, and the row says so in words ("Recovered -- about 12m of downtime earlier today"). Today's bar is outlined to mark it as still being measured, and the left edge is labelled with the span actually measured rather than the configured window.
- Day detail -- Hovering (or tapping) a day opens a card describing it: how much downtime was measured and how severe the day was, any incidents or maintenance windows that overlap it, and how many checks failed out of how many ran. A day with no downtime says so; a day with downtime but nothing recorded against it says that too, rather than leaving a coloured bar unexplained. An outage spanning midnight is counted against each day only for the part that falls within it.
- Response time -- Optionally show response time metrics for each monitor.
- Active incidents -- Any ongoing incidents are displayed with their timeline and status updates.
- Date range -- Visitors choose how far back to look: a week, a month, or the full history the page keeps. The page opens on the last 30 days. The chosen range is part of the address, so a link shares the same view.
- Past incidents -- Resolved incidents from the range being viewed, newest first, five per page. Because the incident list and the history bars cover the same days, a coloured bar always has the incident that explains it somewhere on the page.
Creating a status page
When you create a status page, you configure:
| Setting | Description |
|---|---|
| Name | The display name shown at the top of the page. |
| Slug | The URL-safe identifier (e.g., acme-cloud for status.sentro.dev/acme-cloud). |
| Monitors | Which monitors to display on the page, and in what order. Selected monitors appear at the top of the list in the order visitors see; drag one by its handle to move it, or focus a handle and use the arrow keys. You can also customize display names. |
| Visibility | Anyone can view, only visitors arriving on a signed link, or nobody at all. See private status pages. |
Branding
Customize the look of your status page to match your brand:
- Logo -- An address for a hosted image, set on the status page settings screen. It is shown beside the page name at a fixed height and its own natural width, so a wide logo stays wide rather than being squeezed into a square. A live preview renders it against the background colour you chose, which is where you find out whether a logo drawn for a dark page works on a light one.
- Favicon -- An address for the small icon browsers show in the tab.
- Header text -- A message displayed at the top (e.g., "Acme Cloud Service Status").
- Footer text -- A message displayed at the bottom.
- Appearance -- Dark, light, or your own colours. See below.
- Custom domain -- Point your own domain (e.g.,
status.example.com) at the status page. - Subdomain -- Use a Sentro subdomain (e.g.,
acme.status.sentro.dev). - "Powered by Sentro" badge -- Toggle on or off.
Appearance
Three choices:
| Choice | What it does |
|---|---|
| Dark | The default, and how every page looked before this was configurable. |
| Light | A light page designed as its own thing rather than the dark one inverted — the status colours are deeper, because the shades that read well on near-black wash out on white. |
| Your colours | You set the page background, cards, borders, text and labels yourself. |
The accent colour applies to all three. It is used for links, highlights and the subscribe button, and Sentro picks black or white text on top of it depending on which can be read.
With your own colours, anything you leave empty is worked out from what you did set, so you can change only the background and still get a page that hangs together. Sentro also works out whether your background is light or dark and picks the matching set of status colours.
Operational, degraded and down keep their own colours. They carry meaning, and a page whose "operational" green cannot be read is worse than one that does not quite match the brand.
Logo and favicon addresses must be https. An unencrypted address would make the page report itself as insecure, and it is refused as you type rather than saved and left to break. Status pages accept images from any host, unlike the rest of the dashboard.
A live preview sits next to the controls, and the settings screen warns you when a combination will be hard to read — text against the background, labels against the background, or an accent that will disappear. The warnings are advice, not a block: the page is yours.
Subscribers
Visitors can subscribe to a status page and be told when incidents are opened or resolved. They choose where updates go:
| Channel | What the visitor supplies | How it is confirmed |
|---|---|---|
| An email address | A confirmation email; updates start once the link in it is clicked | |
| Slack | An incoming webhook URL for a channel | A confirmation message posted to that channel |
| Microsoft Teams | An Incoming Webhook connector URL | A confirmation message posted to that channel |
| Discord | A channel webhook URL | A confirmation message posted to that channel |
| Google Chat | A space webhook URL | A confirmation message posted to that space |
| Mattermost | An incoming webhook URL | A confirmation message posted to that channel |
| Webhook | Any HTTPS address | A confirmation payload posted to it |
Chat and webhook destinations confirm themselves: if the confirmation message arrives, whoever pasted the address controls it, so there is nothing to click. A destination that refuses the message is never recorded as subscribed, and the visitor is told to check it.
Every destination must be reachable over HTTPS, and each chat channel only accepts addresses on the service it belongs to — a Slack subscription pointed somewhere other than Slack is refused up front rather than failing quietly during the first real incident. Addresses inside private networks are rejected.
Every message carries a link back to the status page and a link to unsubscribe. You can see the subscriber count from the dashboard.
Subscriptions are only offered on a page anyone can view. On a private page the form is not shown, because accepting a destination would confirm to anyone guessing addresses that the page exists.
When an incident is created or resolved on a monitor assigned to the page, every confirmed subscriber is notified on their own channel. One unreachable destination never stops the others being told.
Display options
| Option | Default | Description |
|---|---|---|
| What the page shows | Uptime and incidents | Choose uptime only, incidents only, or both. Uptime covers the daily history bars, the uptime percentage, the date range and the colour key. Incidents covers the active and past incident lists. The current state of each system always shows, whichever you pick. |
| Show response time | No | Display response time charts for each monitor. |
| Show monitor type | Yes | Display each monitor's type (e.g., HTTP) beside its name. Turn it off for a page aimed at end users who do not need the distinction. |
| History window | 90 days | The furthest back a visitor may look. The page opens on 30 days; visitors can widen it up to this limit. |
| Monitor order | Selection order | The order monitors appear in, controlled by dragging them in the settings. |
| Monitor visibility | Visible | Toggle individual monitors on/off without removing them from the page. |
Plan limits
| Plan | Status pages |
|---|---|
| Free | 1 |
| Starter | 3 |
| Pro | 10 |
| Max | Unlimited |