> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/rollouts/monitor-estate-wide-rollouts/rollout-dashboard-kpis.md).

# Rollout dashboard KPIs

Interpret rollout dashboard counts and success indicators.

Use rollout KPIs to assess rollout health and progress.

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/dzivQyj8aHN5Kvmx8apX/blobs/pNXZQvG5abQdTJUzWNAm/image.png" alt=""><figcaption></figcaption></figure></div>

### When to use this page

Use this page when you need a quick summary of rollout health across devices.

Use it to spot failures, confirm progress, and check the current success rate.

### KPI definitions

* **FAILED** — devices that failed to download or install the software. This count includes **Download failed** and **Installation failed**.
* **SUCCESSFUL** — devices where the package was installed successfully.
* **IN PROGRESS** — devices with rollout jobs that have started but are not yet complete.
* **NOT YET STARTED** — devices with rollout jobs that are scheduled but have not started yet.
* **SUCCESS RATE** — the percentage of rollout jobs that completed successfully.

### Use this dashboard to

* track rollout progress
* identify failures
* measure completion rates

### Interpret the KPIs

Use these quick checks:

* a high **FAILED** count means you should inspect rollout details and affected devices
* a large **IN PROGRESS** count means the rollout is still moving through the estate
* **SUCCESS RATE** helps you judge whether the rollout is completing at the expected level

### Choose the next action

Use the KPI trend with the rollout schedule:

* **NOT YET STARTED** during a future window — continue monitoring.
* **IN PROGRESS** during an active window — inspect rollout details if progress stalls.
* **FAILED** or an unexpected success rate — isolate the affected rollout and batch.

Do not use aggregate counts alone to change a rollout. Confirm the rollout name, batch, scope, and schedule first.

Review the KPI values with rollout scope and schedule context. A count alone does not identify the affected rollout, batch, or root cause.

Use **FAILED** to investigate affected batches. Use **NOT YET STARTED** to verify timing. Use **IN PROGRESS** to continue monitoring within the schedule window.

### Related pages

* [Monitor estate-wide rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/monitor-estate-wide-rollouts) — inspect rollout and batch status
* [Managing rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/managing-rollouts) — take action on rollout jobs


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/rollouts/monitor-estate-wide-rollouts/rollout-dashboard-kpis.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.