When a Bolstat check fails, it will trigger an incident. These incidents alert you about something that went wrong and allow you to manage it.
Incidents evolve along the following lifecycle:
Open: An incident starts in the open status. During the open status Bolstat will try to alert you team about this incident.
Acknowledged: When someone acknowledges the incident, any escalation and notifications to other team members will pause so the team member handling the incident can manage it.
Resolved: After the issue has been fixed, the incident will close and take the resolved status.
Every incident can have one of three different severity levels:
Critical: Critical incidents are meant to alert you about your most critical infrastructure components. These incidents will escalate throughout your whole team and will use all their notification methods.
Minor: Minor incidents are important, but not time-sensitive. The first step within your notification policy will be triggered, but not escalated to other team members. Team members can also set their own contact preference for these incidents.
Info: Info incidents are meant to inform only. Team members will not receive any notifications about these. Only the dashboard and integrations like Slack will show the incidents.