SLAs only checked after a complaint
SLA breach rate by work type and priority, with an alert when it crosses a threshold.
Solutions by team
IT has to prove services are stable and spot weak points early. The IT module tracks incidents and service requests, response and resolution time (MTTR), SLA breach rate, change failure rate and the availability of each service.
Free plan with no time limit · No card required · Sample workspace ready in minutes
SLA breach rate by work type and priority, with an alert when it crosses a threshold.
Incident count, P1 incidents and MTTR by service show which systems need investment.
Change failure rate next to the number of deployed changes per service.
Every industry has a metric linking downtime to the business, such as the MRR exposed during an outage for a SaaS company.
Same team, metrics in each industry's own terms.
| Metric | Definition | Unit |
|---|---|---|
| Incidents | Number of incident-type tickets opened in the period, by open date. | Count |
| P1 incidents | Number of highest-priority incidents (P1, critical) opened in the period. | Count |
| Mean time to resolve (MTTR, hours) | Average hours from open to resolution for incidents resolved in the period.= it_incident_hours_total / Resolved incidents | Number |
| Average first response time (hours) | Average hours from ticket creation to first response, across all tickets opened in the period.= it_response_hours_total / IT support tickets | Number |
| SLA breach rate | Tickets breaching SLA divided by tickets opened in the period.= SLA breaches / IT support tickets | Ratio (%) |
| Change failure rate | Failed changes (failed or rolled back) divided by changes deployed in the period.= Failed changes / Changes deployed | Ratio (%) |
| Service availability | One minus outage minutes divided by the service's planned operating minutes in the period.= 1 - Outage minutes / it_planned_minutes | Ratio (%) |
| Outage minutes | Total minutes a service was down or disrupted, counted on the day the outage started. | Number |
The catalogue covers many ticketing and incident tools; if yours is missing, use the custom REST API connector or a file.
No. DataxLand analyses the incident and SLA data you already have; real-time monitoring stays in your dedicated tools.
Yes. Private deployment is part of the Enterprise plan and runs on AWS, GCP, Azure, Kubernetes or on-premises servers, including air-gapped environments; see the Private deployment page.
Free plan with no time limit · No card required · Sample workspace ready in minutes