> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/power-monitor/mapeamento/metricas-de-capacidade.md).
# Capacity Metrics
Follow and trigger the three scans that feed the Capacity Dashboard: capacity list, Capacity Units consumption and daily operations per item.
The Mapping **Capacity Metrics** screen brings together the **three scans** that feed the Capacity Dashboard and the consumption screens: the **capacity list** (read through the Admin API), the **Capacity Units (CU) consumption** per capacity and the **daily operations per item**. The last two are read from the **Microsoft Fabric Capacity Metrics App** installed in your tenant. Here you see the last run of each scan and can trigger any of them right away.
**How to access:** *Mapping › Capacity and cost › Capacity Metrics*. Only **Administrators** can access the screen and the actions.
Capacity Metrics
## What it is for
* Confirm that Capacity Units consumption is being collected and that the Capacity Dashboard is up to date.
* Force a collection after configuring the Capacity Metrics Source or turning on monitoring for a capacity.
* Find out which of the three scans failed when the Capacity Dashboard or the Consumption History show outdated data.
## Screen components
The screen has two cards: **What is collected** and **Scans in this collection**.
### What is collected
**What it is:** a card with the description of the three scans and, in the footer, the links **View collected data in Capacity Dashboard →**, **View collected data in Consumption History →** and **View collected data in Consumption Metrics →**.
### Scans in this collection
**What it is:** a table with one row per scan and the columns **Scan**, **Last run**, **Status** and the **Run now** button.
Scans in this collection card
| Scan | What it collects | Source | Automatic frequency |
| ------------------------ | ------------------------------------------------------------------- | -------------------- | ---------------------------------------- |
| **Capacity** | Inventory of capacities (name, SKU, region, state) | Admin API | Once a day, at **00:00** (Brasília time) |
| **Capacity Consumption** | CU consumption of the capacities | Capacity Metrics App | Every 5 minutes |
| **Item Operation** | Daily operations per item (consumption per item, operation and day) | Capacity Metrics App | Every 5 minutes |
The **Status** of each row can be **Running** (blue), **Completed** (green), **Failed** (red) or **Never run** (gray). Each row has its own button, and the scans can run at the same time.
**How to use Run now:**
1. In the row of the desired scan, click **Run now**. There is no confirmation modal.
2. **Scan queued. The status updates by itself when it finishes.** appears and the button shows **Running…** (disabled).
3. When it finishes, Power Monitor notifies you with **Scan completed.** or **The scan finished with a failure. See the details in Scan Logs.**, and the **Last run** of the row is updated.
**Full history:** the **View full history in Scan Logs →** link opens [Scan Logs](/en/power-monitor/mapeamento/logs-de-scans-e-re-execucoes.md) filtered by the three types (**Capacity**, **Capacity Consumption** and **Item Operation**).
### Run history
**What it is:** the **Run history** table, below the scans, with the runs of this screen's scans from the most recent to the oldest, with an items-per-page selector and pagination.
| Column | Content |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------- |
| **Trigger** | **Scheduled** or **Manual** (for manual runs, hover over the person icon to see who triggered it) |
| **Scan** | Which of this screen's scans ran |
| **Started** / **Finished** / **Duration** | Run times; while the run is in progress, **Duration** shows the elapsed time live |
| **Status** | Run status |
| **Items processed** | Number of items handled by the run |
| **Error** | Icon with the run's error message (hover over it) |
**What it is for:** checking the latest runs and the error of a failure without leaving the screen.
{% hint style="info" %}
The **Capacity** scan is the same capacity inventory as the [Capacities](/en/power-monitor/mapeamento/capacidades.md) screen, which also brings the history per run and the changes modal. Use either one to trigger the inventory.
{% endhint %}
## Rules and behavior
* **Capacity Consumption and Item Operation** depend on the **Fabric Capacity Metrics App** and on the **Capacity Metrics Source** configured in *Settings › Monitoring*, besides monitoring turned on in at least one capacity for the automatic collection. Without the source configured, the run ends without collecting anything (no item processed). See [Enable Capacity Monitoring](/en/power-monitor/monitoramento/capacidades/ativar-monitoramento-de-capacidade.md).
* **Frequency:** the **Capacity** scan can have its **Frequency** changed to **Daily**, **Weekly** or **Monthly** and be turned off in *Settings › Monitoring › Scans and Collections* (**Capacity Inventory**). The two Capacity Metrics App scans run every 5 minutes and do not have this option. The **Run now** button is not affected by these settings.
* **Later processing:** the consumption collected here is turned into hourly metrics, baseline and anomalies by the processes followed in [Consumption Metrics](/en/power-monitor/mapeamento/metricas-de-consumo.md).
* **Last run:** comes from the same record as Home, not from the window of days of Scan Logs.
* **How much it consumes:** **Capacity Consumption** and **Item Operation** run DAX queries on the Capacity Metrics App every 5 minutes, the largest CU consumption on the platform. This consumption falls on the capacity that hosts the **app workspace**, not necessarily on the monitored capacity. The footer of the **Scans in this collection** card shows the matching sentence, with an **i** that explains the consumption:
* app on a capacity: *The capacity consumption and item operation scans consume Fabric capacity to update the data.*, and the **i** names the capacity;
* app in a Pro or Premium Per User workspace: no sentence, because the queries consume no capacity;
* app location unknown: *... may consume Fabric capacity, depending on where the Capacity Metrics app is installed.*
Microsoft recommends installing the app in a Pro workspace to avoid throttling. See [Fabric capacity consumption](/en/power-monitor/configuracoes/monitoramento.md#fabric-capacity-consumption).
## Step by step
{% stepper %}
{% step %}
### Open the screen
In *Mapping › Capacity and cost › Capacity Metrics*.
{% endstep %}
{% step %}
### Check the state of the scans
Look at the **Last run** and the **Status** of **Capacity**, **Capacity Consumption** and **Item Operation**.
{% endstep %}
{% step %}
### Trigger the collection
Click **Run now** on the late scan and wait for the status to become **Completed**. If it fails, open **View full history in Scan Logs →**.
{% endstep %}
{% step %}
### Check the data
Open the [Capacity Dashboard](/en/power-monitor/dashboards/dashboard-de-capacidade.md) or the [Consumption History](/en/power-monitor/monitoramento/historico-de-consumo.md).
{% endstep %}
{% endstepper %}
## Frequently asked questions
Capacity Consumption completed, but the dashboard is empty. Why?
Check whether the **Capacity Metrics Source** is **Configured and validated** and whether there are capacities with monitoring turned on in *Settings › Monitoring*. Without the source, the scan ends without processing items. See [Enable Capacity Monitoring](/en/power-monitor/monitoramento/capacidades/ativar-monitoramento-de-capacidade.md).
Why are there scans every 5 minutes but the dashboard is delayed?
The scans read what the Capacity Metrics App already has available: if the app has not updated its data yet, there is no new data to collect. **Run now** only anticipates the reading.
What is the difference between this screen and Consumption Metrics?
This screen collects the raw consumption of the capacities. The [Consumption Metrics](/en/power-monitor/mapeamento/metricas-de-consumo.md) screen follows the processes that turn it into hourly metrics, baseline and anomalies, and has no manual trigger.
## Related pages
* [Capacity Dashboard](/en/power-monitor/dashboards/dashboard-de-capacidade.md)
* [Consumption History](/en/power-monitor/monitoramento/historico-de-consumo.md)
* [Monitoring › Consumption Metrics](/en/power-monitor/monitoramento/metricas-de-consumo.md)
* [Capacities](/en/power-monitor/mapeamento/capacidades.md)
* [Consumption Metrics (Mapping)](/en/power-monitor/mapeamento/metricas-de-consumo.md)
* [Enable Capacity Monitoring](/en/power-monitor/monitoramento/capacidades/ativar-monitoramento-de-capacidade.md)
* [Mapping](/en/power-monitor/mapeamento.md)
---
# 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.powermonitor.com.br/en/power-monitor/mapeamento/metricas-de-capacidade.md?ask=&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.
