An SLA policy in Scrubbe defines the time targets your team commits to for acknowledging and resolving incidents at a given priority level. Once SLA tracking is enabled for your organization, Scrubbe measures every open incident against the matching policy, notifies your team when targets are at risk, and can automatically escalate incidents that breach their thresholds. SLA policies are the mechanism that turns incident response from informal effort into measurable, accountable practice.Documentation Index
Fetch the complete documentation index at: https://docs.scrubbe.com/llms.txt
Use this file to discover all available pages before exploring further.
Enabling SLA tracking
SLA tracking is controlled by your IMS configuration. SetslaEnabled to true to activate it, and set autoEscalate to true to let Scrubbe escalate breached incidents without manual intervention:
autoEscalate is true, Scrubbe routes a breached incident to the escalationContact defined in the matching SLA policy.
Creating an SLA policy
Policy fields
Identity
Identity
| Field | Description |
|---|---|
name | Human-readable label for the policy |
priority | The incident priority this policy applies to: LOW, MEDIUM, HIGH, or CRITICAL |
applicableTeam | Email or identifier of the team this policy governs |
Response targets
Response targets
| Field | Description |
|---|---|
responseTimeMinutes | Maximum minutes from OPEN to ACKNOWLEDGED before the response SLA breaches |
responseThreshold | Target compliance rate as a percentage (e.g. 90 means 90% of incidents must be acknowledged within the response time) |
Resolution targets
Resolution targets
| Field | Description |
|---|---|
resolveTimeMinutes | Maximum minutes from OPEN to RESOLVED before the resolve SLA breaches |
resolveThreshold | Target compliance rate as a percentage |
Escalation and uptime
Escalation and uptime
| Field | Description |
|---|---|
escalationContact | Name or identifier of the person or team to notify on breach (used when autoEscalate is enabled) |
uptimeTarget | Target uptime percentage for this priority tier (e.g. 99.9) |
How SLA tracking works
When a ticket is created with a given priority, Scrubbe looks up the SLA policy for that priority and setsslaResponseTimeMinutes and slaResolveTimeMinutes on the ticket. Timers start when the ticket status becomes OPEN.
Scrubbe sends a warning notification at the halfway mark for both the response and resolution windows. If the window closes without the required status transition, the ticket is marked as breached.
Breach types
| Breach type | Meaning |
|---|---|
NONE | No SLA has been breached on this ticket |
RESPONSE_BREACH | The ticket was not acknowledged within responseTimeMinutes |
RESOLVE_BREACH | The ticket was not resolved within resolveTimeMinutes |
BOTH | Both the response and resolution windows were exceeded |
slaBreachType field.
Managing policies
| Operation | Endpoint |
|---|---|
| List all policies | GET /api/v1/sla-policies |
| Get a specific policy | GET /api/v1/sla-policies/:id |
| Update a policy | PUT /api/v1/sla-policies/:id |
| Delete a policy | DELETE /api/v1/sla-policies/:id |
| View SLA analytics | GET /api/v1/sla-policies/analytics |
SLA policy analytics
GET /api/v1/sla-policies/analytics returns compliance data across your policies — breach counts by priority, average response and resolution times, and compliance rates against your configured thresholds. Use this endpoint to identify which priority tiers need staffing or process changes.