SLA Breach Escalation Alert Log

This is the compliance audit trail for SLA breaches. Every resolved issue that exceeded its SLA target is logged here with its breach multiplier — how many times over the target it took to resolve. A ticket that took 2.8 days when the SLA was 1 day is a 2.8× breach. For regulatory compliance, this log provides the evidence that breaches occurred and documents their severity.

What you can conclude

• Breach multipliers above 3× represent the most serious SLA failures — these warrant formal documentation and root-cause review.
• A pattern of moderate breaches (1.2–2×) across many issues suggests a systemic capacity gap rather than isolated failures.
• A log with no entries in a period indicates full SLA compliance — the strongest possible compliance evidence.

How this chart works

Audit table showing all resolved issues that breached their SLA target. Columns: resolution date, issue key, project, priority, SLA target, actual resolution time, breach multiplier, and severity classification (major / critical). Use the project and date filters to scope the audit period.