Overview
When an SLA is breached, SQIBS opens a low urgency incident in a service you choose, and that service's escalation policy notifies the right people. Set up a dedicated team, policy and service for it, kept apart from your operational alerts.
You need
Global Admin roleTime
About 10 minutesResult
A low urgency incident per SLA breachHow it works
1
SLA breachedA target in an SLA is missed.
2
Incident opensLow urgency, in your SLA notification service.
3
Policy runsThe service's escalation policy starts.
4
People notifiedBy their notification rules.
Set it up
- Create a team for SLA breach notifications, for example SLA Alerts.
- Invite the people who should hear about breaches.
- Create an escalation policy for them.
- Create a service with that policy. It needs no API or email integration.
- Choose that service for breach notifications in the SLA.
Keep SLA notifications apart from production services, keep the escalation simple, and review the team's members from time to time.