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 role
Time
About 10 minutes
Result
A low urgency incident per SLA breach

How it works

1
SLA breached
A target in an SLA is missed.
2
Incident opens
Low urgency, in your SLA notification service.
3
Policy runs
The service's escalation policy starts.
4
People notified
By their notification rules.

Set it up

  1. Create a team for SLA breach notifications, for example SLA Alerts.
  2. Invite the people who should hear about breaches.
  3. Create an escalation policy for them.
  4. Create a service with that policy. It needs no API or email integration.
  5. 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.