Incidents · Guides
Show incidents on a status page
Status, My Beast's uptime checks, works with Incidents both ways: a down opens an incident, and the incidents you choose tell your users on the public page.
Connect Status
Both products must be in the same project. Then:
- In Incidents' project, make a server secret on Settings → Keys, as Open incidents from your systems says. Label it
status. - In Status, open the project's Settings. Under Who gets told, choose Connect beside Incidents.
- Give the Incidents address,
https://services.my-beast.com/incidents, and paste the server secret. Status checks it with Incidents before it is saved; nothing is opened there.
The row then says Connected. If Incidents later refuses the secret, Status says so on the same row, and downs reach its alert channels alone until a new one is pasted.
When a monitor goes down
A confirmed down opens an incident with the monitor's severity, named after the monitor, and your team is told as for any other. Its recovery resolves the incident. While one down is open, the same monitor going down again adds to that incident instead of opening another.
On the incident's page, Declared says “By Status, through the API” and links back to the monitor. If Incidents doesn't take the call, Status's alert channels tell people instead. Each downtime in Status also links to Incidents' What happened then, with what every product had at that moment.
Show an incident on the page
An incident appears on your public status page only when someone chooses it. On the incident's page, under Run it, choose Show on the status page. The head then says On the status page, and Take off the status page hides it again. Either choice is on the timeline and in the audit log, because it puts your words in front of everyone.
Status reads the incidents to show every minute, so a change can take a minute to appear. A resolved incident stays on the page for 14 days; a declined one leaves it at once.
What the page shows
For each incident shown, the public page has:
- its reference, title and severity;
- its status, when it began and when it was resolved;
- its public updates, oldest first, each with the status it had then: the updates you posted and the messages posted with a change of status or severity.
What never shows
Your own status page can show the same: the API answers the incidents to show, with a server secret.