> For the complete documentation index, see [llms.txt](https://docs.autopilotmonitor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autopilotmonitor.com/portal-guide/sla-compliance.md).

# SLA Compliance

If you've committed to enrollment service levels — internally or contractually as an MSP — this page reports against them over a 1/3/6-month window.

## Configuring targets

Targets are defined under **Settings → Tenant → SLA Targets** (the page links you there if none exist yet). Three targets are available, each optional — only configured targets are evaluated:

* **Enrollment Success Rate** (e.g. ≥ 95 %)
* **Max (P95) Enrollment Duration** (e.g. ≤ 60 minutes)
* **App Install Success Rate**

## What you see

* An **overall status banner** — *All SLA Targets Met* or *SLA Targets Breached* — with per-target check marks.
* **Gauge charts** per target comparing the current value to the target (the duration gauge is inverted — lower is better).
* **This week** stat cards (sessions, succeeded, failed, duration violations) and a **weekly trend** line chart of success rate over the selected months.
* **Top Failing Apps** and an **App Install Summary** when app data exists.
* The **SLA Violators** table — every offending session with device (linked), serial, duration, status, a **violation-type badge** (Duration / Failed / Both), and the failure reason. Or, on a good day, a green *No SLA violations*.

{% hint style="info" %}
Metrics are cached for speed — the header shows when they were computed, and **Refresh** recomputes on demand.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.autopilotmonitor.com/portal-guide/sla-compliance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.