Overview

Incident response thresholds set how fast each incident must be acknowledged and resolved, by priority. When a target is missed, SQIBS treats the incident as high urgency and escalates it. They are timers on each incident, not an SLA calculator: for uptime percentages use the SLA tracker.

Set per
Priority P1 to P5
Levels
Global, team, service
On breach
High-urgency notifications and escalation

The three timers

Timer Meaning Example
MTTA Time allowed to acknowledge, from creation. 5 minutes: acknowledge within 5 minutes.
MTTR Time allowed to resolve, from creation. 2 hours: resolve within 2 hours.
Retrigger After an MTTR breach, how long until SQIBS re-triggers the still-unresolved incident. 15 minutes.

A value of 0 turns that timer off. Retrigger must be 0 or at least 5 minutes.

What happens on a breach

Start
Incident opens
The timers for its priority start.
Breach
MTTA or MTTR missed
The incident is marked as breached.
Escalate
High-urgency notifications
Escalation runs until it is acknowledged (MTTA) or resolved (MTTR), or the policy ends.

Where to set them

Level Where Who Applies to
Global WORKSPACE > Incident Response Threshold Global Admin Every team without its own settings
Team The team's Incident Response Threshold tab Global Admin, Team Manager Services in the team without their own settings
Service The service's Incident Response Threshold tab Global Admin, Team Manager That service

When the global setting is on, teams and services show it as Inherited from Global. To let a team (and its services) use its own values, the Global Admin adds the team under Teams allowed to override global configuration.

Suggested starting points

Priority MTTA MTTR Retrigger
P1 Very short Very short Frequent
P2 Short Short Regular
P3 Moderate Moderate Moderate
P4 Long Long Infrequent
P5 Optional Optional Optional

Match thresholds to what you promise customers, and retrigger often enough to avoid a missed incident but not so often that it becomes noise.

With the SLA tracker

When you set up an SLA, you can choose to let its recommended MTTA and MTTR values override the thresholds of the services in the SLA's projects (Incident Threshold To Override). Use it when response times are part of a contract.