For whom: on-duty engineer, support. Required rights:
statuspage.incidents for incidents, statuspage.maintenance for scheduled work.Start an incident.
1
What happened?
The short headline that the visitor reads first, without the internal terms: “Personal Account Not Opening,” not “5xx on api-gw.”
2
How serious is this?
The severity of the color on the page depends.| Seriousness | What Does | Mean?
|---|---|
| Minor | Part of the visitors notice the inconvenience, the service works |
| Serious | Many cannot use the | service
| Critical | Service not available to |
3
What's wrong?
Mark the components that have stopped working, and next to them, a mark will appear on the page, and the overall state will be recalculated.
4
What do we tell the visitors?
The first entry in the chronology. It’s the one that shows the incident on the page, so it’s worth saying two things: what you already know and when the next update will be.
Chronology
Then the incident lives on in the records, and each recording puts it into one of these states:
You can add a record without changing your state, if you have nothing to say other than “getting on with it,” and it appears on the page as soon as it’s sent.
Drafts
The incident can be saved with a draft: it is visible in the panel and not visible to visitors, so it is convenient to prepare an announcement while the cause is still being clarified. The first entry in the chronology publishes the incident. After that, you can’t delete it, just close it, and the delete button disappears: the page has already shown visitors that something is happening, and silently erasing it would be a hoax. The draft is removed freely.The tape didn’t make it.
Sometimes the panel says that the record is saved but not delivered to the page, which means exactly what it says: it’s in the panel, it’s not on the page yet, you don’t need to rewrite the text, you need to repeat the submission, if the page does not respond for more than a couple of minutes, you have to deal with its server.Planned work
The service window warns you in advance, and that’s the difference between “they’re out of order” and “we’re warned,” and there are four questions: what’s the job, when (beginning and ending in your time zone, the visitor will see the time in their own), what’s not available and what to warn about. The noted components during the work are shown as planned, not as a failure. The window goes through four states: planned, executed, completed, canceled. You can switch them manually, or you can tick “Start Automatically” and “Complete Automatically” - then the page will do it itself in time.From support.
A message that turns out to be a general failure is raised into a page incident directly from the support module, and a draft is created with a reference to the original support incident, and it is published by a person: the decision to show the failure to all customers should not be made automatically.Verification
The published incident is visible on the public page, and its records go in chronology in the order in which you sent them.
Typical errors
The incident has been posted and the page is still green.
The incident has been posted and the page is still green.
Check if the affected components are marked.The incident without them is shown in the tape, but the general condition does not change.
Planned work does not start automatically
Planned work does not start automatically
Auto-starts the page server. If it is not responding at this time, translate the window to “Run” manually.
