> 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/principais-funcionalidades/monitoramento-de-capacidades.md).

# Capacity Monitoring

How Power Monitor tracks the consumption of Fabric, Premium and Embedded capacities in Capacity Units, with history, comparisons, anomalies, cost and alerts.

Power Monitor continuously tracks the **consumption of the capacities** in your tenant in **Capacity Units (CU)**, with history, comparisons, per-item anomaly detection, cost and alerts when a capacity approaches its limit.

## Where the data comes from

Consumption is read from the **Microsoft Fabric Capacity Metrics** app, installed in your tenant, **every 5 minutes**. The capacity inventory (name, SKU, region, administrators) comes from the Power BI admin APIs.

{% hint style="warning" %}
**Prerequisite:** the Fabric Capacity Metrics app must be installed and configured as the **Capacity Metrics Source** in **Settings › Monitoring**, and monitoring must be turned on for each capacity. See [Enable Capacity Monitoring](/en/power-monitor/monitoramento/capacidades/ativar-monitoramento-de-capacidade.md).
{% endhint %}

## What is tracked

| Metric                                       | What it means                                                                                                          |
| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| **Cumulative usage (Cumulative CU usage %)** | How much of the capacity is committed, taking Fabric smoothing into account. It is the basis for the usage limit alert |
| **Interactive consumption**                  | Operations triggered by users, such as opening reports and running queries                                             |
| **Background consumption**                   | Refreshes of models, pipelines, notebooks and other asynchronous workloads                                             |
| **Capacity Units (s)**                       | Absolute consumption per operation and per item, used in rankings and comparisons                                      |

## Screens

| Screen                                           | What it is for                                                          |
| ------------------------------------------------ | ----------------------------------------------------------------------- |
| **Monitoring › Capacities**                      | Current and recent consumption of each capacity                         |
| **Consumption Comparison**                       | Compare consumption across periods, capacities, workspaces or items     |
| **Consumption History**                          | Evolution of consumption over time                                      |
| **Consumption Metrics**                          | Detailed consumption per item and operation                             |
| **Consumption Anomalies**                        | Items that consumed above their baseline for the last 7 days            |
| **Capacity Cost**                                | Daily cost per capacity, based on Azure (requires cost read permission) |
| **Capacity Dashboard** and **Capacity Overview** | Consolidated view for management                                        |

The **Capacities** area of the menu brings together all these screens, plus [Capacity Governance](/en/principais-funcionalidades/governanca-de-capacidade.md) and Capacity Actions. See [Capacities](/en/power-monitor/capacidades.md).

## Alerts

* **Capacity Usage Limit:** cumulative usage at or above **80%**.
* **Capacity Background Usage:** bands of 50%, 70%, 80% and 100%.
* **Consumption Data Unavailable:** no new data for more than 45 minutes (for example, a paused capacity).
* **Item Consumption Anomaly** and **Capacity cost** above the average.

See [Real-time alerts](/en/principais-funcionalidades/alertas-em-tempo-real.md).

## Supported capacities

* **Microsoft Fabric (F-SKU)** and **Power BI Premium per capacity (P-SKU)**: consumption monitored through the Fabric Capacity Metrics app, for the capacities it reports.
* **Power BI Embedded (A-SKU)**: inventory and governance (pause, resume, change size (SKU)) through Azure.
* **Pause, resume and change size (SKU)** are available only for capacities that are Azure resources (**F** and **A**).

## Related pages

* [Capacities](/en/power-monitor/monitoramento/capacidades.md)
* [Capacity Governance](/en/principais-funcionalidades/governanca-de-capacidade.md)
* [Consumption Anomalies](/en/power-monitor/monitoramento/anomalias-de-consumo.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/principais-funcionalidades/monitoramento-de-capacidades.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.