Create an incident
Inform your client base of any downtime or unavailability of your services by creating an incident on your status page.
- Click Incidents from the left sidebar.
- Click Create incident.
- Enter the name of the incident.
- Select an incident status.
- Enter a message to include in the incident update.
- Select the affected monitors by this incident.
- Select the status pages that should display incident details.
- Select whether or not to send notifications to your subscribers for this incident.
- Click Save Incident.
More information on the fields in the incident form:
An incident is identified by a name that represents the issue as a whole. "DB connectivity issues," "API timeouts," and "DNS issues" are examples.
There are four different statuses for incidents. A state will be specified when you create or update an incident.
Investigating - when you observe the symptoms of an issue, you are unaware of the underlying cause.
Identified - you've figured out what caused the event and are working on a solution.
Monitoring - you think you've solved the problem and are waiting for the symptoms to go away.
Resolved - the fundamental cause of the problem has been identified, and your systems are now operating at full capacity.
When you create or update an incident, you may provide a brief note that describes the current situation.
By specifying which monitors are affected by an incident, your component status and incident updates stay in sync, and your users have a complete view of service health. If you're on a Business plan or higher and have the component subscription capability turned on, you can fine-tune your subscribers' notifications.
All status pages that you select in this step will display incident messages
Notifications can be sent to your subscribers whether you want them to or not. In order to send notifications, you need to indicate that one or more monitors were affected by the incident.