> 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/usage-metrics.md).

# Usage Metrics

Usage Metrics is the informational overview of how your tenant uses Autopilot Monitor — useful for capacity questions, adoption reporting, and a quick feel for the numbers behind the fleet.

## What you see

* **Sessions** — total / today / last 7 days / last 30 days, and succeeded / failed / in progress / success rate.
* **Deployment Types** — user-driven vs. pre-provisioned (White Glove) with counts, percentages, and bars.
* **Apps & Scripts** — average apps per session (plus total unique apps), average platform-script and remediation-script executions per session.
* **Users** — unique portal users (90 days), daily logins, and 7-/30-day active users.
* **Performance** — average, median, **P95**, and **P99** enrollment durations. The percentiles are the honest numbers for planning: the median tells you the typical experience, P95/P99 tell you what your unluckiest users live through.
* **Hardware** — top manufacturers and top models with counts and shares.

The page is read-only; metrics are cached with a computed-at note and a **Refresh** button.


---

# 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/usage-metrics.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.