Overview
The SLA tracker measures uptime against your target from real incidents, so you do not keep a spreadsheet. It warns your team before the allowed downtime runs out and opens an incident when the SLA is breached.
How it works
SLA % = (total time - downtime) / total time x 100, and allowed downtime = total time x (1 - SLA % / 100).
| Target | Allowed downtime in 30 days |
|---|---|
| 99% | about 7 hours 12 minutes |
| 99.9% | about 43 minutes |
| 99.99% | about 4 minutes |
Before you start
- Create projects that group the services the SLA covers.
- Prepare a team and service for SLA alerts, with an escalation policy that notifies all the right people at its first level. See SLA breach notifications.
Create an SLA
Go to SLA under WORKSPACE and click Add SLA.
| Field | What to enter |
|---|---|
| SLA Name | Usually the product name. |
| Description | What this SLA covers. |
| Timezone | Used for every time-based calculation, including the window. |
| Projects | Choose a team, then one or more of its projects. |
| SLA Time Range | The window that resets: Day (a number of days), Month (a number of months) or Year, with the starting month and day. The start can be in the past. |
| SLA | The target percentage, for example 99.9. |
| Notify Reminder % | Warn when this share of the allowed downtime is used, for example 80. |
| Notify Breach Again | How long to wait before notifying again while the SLA stays breached. 0 turns it off. |
| Priorities | Which incident priorities count against the SLA, for example P1 and P2. |
| Service Level SLA Escalation | The team and service where SQIBS opens the reminder and breach incidents (at P5). |
Optionally turn on Incident Threshold To Override: the recommended MTTA and MTTR for the selected priorities then replace the incident response thresholds of the services in these projects. Recommended when response times are contractual.
Click Save.
Change or delete an SLA
Open Show More Details on the SLA, then Edit or Delete. Changes apply to the current window only; earlier reports stay as they were.
SLA report
SLA Report under REPORTS shows, for each SLA: the time range, current and target SLA, remaining and allowed downtime, downtime in the current window, and the incidents that affected it.
Common questions
Where do I set response (MTTA) and resolution (MTTR) targets? In incident response thresholds, per priority.
Which SLA models are supported? Uptime over fixed day, month or year windows (for example a rolling 30-day window, a calendar month, or a custom number of days), plus per-incident response and resolution targets through thresholds.