A status page is a public web page that tells your visitors whether your services are working. Vimonto Deploy builds it from the checks it already runs: a site's uptime check, a heartbeat or a server. When something goes wrong, you post an incident and keep visitors informed with updates; planned work goes on the page as scheduled maintenance.
Every status page has its own address, /status/{address}, that anyone can open without signing in. It shows only the names you choose: never a domain, server name or IP address unless you type it yourself.
Create a status page
- Click Status pages in the top navigation.
- Click New status page.
- Enter a Name: the title of the public page, such as "Acme status".
- Check the Address. It is filled in from the name; use lowercase letters, digits and dashes. Every address is unique across Vimonto Deploy.
- Optionally add a Description, shown below the title.
- Click Create status page.
The page is published straight away, but it shows nothing until you add components.
Add components
A component is one line on the status page, with its current state and a bar of the last 90 days. Open the status page and, under Components:
- Click Add component.
- Choose what it Shows:
- Site uptime: a site's uptime check, every 15 minutes.
- Heartbeat: a heartbeat of one of your servers, which a scheduled job calls.
- Server online: whether a server is reachable.
- Choose the site, heartbeat or server. You only see servers you have access to, if your access is limited to teams.
- Enter the Public name: what visitors see, such as "Website" or "API".
- Click Add component.
To group components, click Add section and give it a name, such as "Websites". Choose the Section when you add or edit a component. Components without a section are shown at the top, without a heading.
Use the arrows next to a component or section to change the order. Edit changes a component's public name and section; to follow something else, remove the component and add a new one. Removing a component or section only changes the status page: the checks behind it keep running.
What the public page shows
At the top, one line sums up the state of everything on the page:
| Headline | When |
|---|---|
| All systems operational | Every component works, or there are no components yet. |
| Under maintenance | A scheduled maintenance is in progress. |
| Degraded performance | At least one component is degraded. |
| Partial outage | At least one component is down. |
| Major outage | Every component that has data is down. |
Each component shows one of these states:
| State | Site uptime | Heartbeat | Server online |
|---|---|---|---|
| Operational | The site is up. | The last ping came in time. | The server is active and its monitoring agent reports. |
| Degraded performance | The last check failed, but not two in a row. | ||
| Outage | Two or more checks in a row failed. | The ping did not come in time. | The server is disconnected, or its agent has not reported for 10 minutes. |
| Under maintenance | A scheduled maintenance for this component is in progress. | ||
| No data | Checks are off, or the site was not checked yet. | The heartbeat was never called. | The server is still being set up. |
An open incident can make a component look worse than the checks say, depending on its impact (see below).
The 90-day bars
Below each component, a bar has one block per day for the last 90 days, coloured by the uptime of that day: green for 100%, light green for 99% or more, orange for 95% or more and red below that. Grey means no data. Hover over a block to see the date and the uptime. On a phone, the bar shows the last 30 days.
- Site uptime comes from the site's uptime checks, which are kept for 90 days.
- Heartbeats and servers are sampled every 5 minutes while they are on a status page. Their bar starts on the day you add them.
The public page reloads by itself every two minutes.
Post an incident
When something is wrong, open the status page and go to Incidents:
- Click Post incident.
- Enter a Title, such as "Checkout fails".
- Choose the Impact:
- None: the incident is listed, but no component changes.
- Minor (degraded performance): affected components show at least Degraded performance.
- Major (outage): affected components show Outage.
- Choose the Status: Investigating, Identified, Monitoring or Resolved.
- Write a Message: the first update visitors read.
- Tick the Affected components.
- Click Post incident.
While it is open, the incident is shown at the top of the public page. Click Post update to add to its timeline: choose the new status and write what changed. Every update is shown with its date and time. An update with the status Resolved closes the incident, and the affected components show what the checks say again.
An incident without affected components still changes the headline, by its impact.
Schedule maintenance
- On Incidents, click Schedule maintenance.
- Enter a Title and the Starts and Ends date and time. The time zone is shown next to the field labels.
- Choose the Status (usually Scheduled), write a Message and tick the Affected components.
- Click Schedule maintenance.
Until it starts, the maintenance is listed under Scheduled maintenance on the public page. From the start time, it is In progress and its components show Under maintenance, whatever their checks say. At the end time it is Completed. Post an update with In progress or Completed to start or finish it earlier.
Incident history
Resolved incidents and finished maintenance stay under Past incidents on the public page for 90 days. In the app, Incidents lists the 50 most recent. Edit changes an incident's title, impact, affected components or maintenance window; Delete removes it with its updates. To close an incident, post an update that resolves it rather than deleting it, so visitors can see what happened.
Settings
Under Settings you change the Name, Address and Description, and:
- Brand colour: the colour of the line at the top of the page and of its links, such as
#f95600. Leave it empty for the default. - Published: switched off, the public address answers "not found". Members of your organization still see the page, with a note that it is a preview.
Changing the address breaks links to the old one. Delete status page removes the page and its incidents; the checks behind it keep running.
Who can change status pages?
Every member can see the status pages. Owners, administrators, managers and developers can create and change them, post incidents and schedule maintenance; viewers cannot. Changes are recorded in the audit log.
Frequently asked questions
Can I use my own domain for a status page?
Not yet. Status pages are served at /status/{address} on Vimonto Deploy.
Can visitors subscribe to updates?
Not yet. Visitors open the page to see the current state; it reloads by itself every two minutes.
Does the status page show my domains or IP addresses?
No. Only the names you type for components and incidents appear. A component called "Website" stays "Website", whatever site it follows.
The page shows "No data" for a component. Why?
The site has not been checked yet or its uptime checks are switched off, the heartbeat was never called, or the server is still being set up. A removed site, heartbeat or server also leaves its component without data; remove the component in that case.