> 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/perguntas-frequentes/duvidas-gerais/o-que-e-o-power-monitor.md).

# What is Power Monitor?

Summary of what Power Monitor is and what it does in your Microsoft Fabric and Power BI environment.

**Power Monitor** is a SaaS (Software as a Service) platform from [Power Tuning](https://powertuning.com.br/) for **monitoring, governance, data quality, and audit** of **Microsoft Fabric** and **Power BI** environments.

Instead of finding out about problems when a user complains, you are **notified automatically**, before the impact reaches end users.

### What does Power Monitor do?

Power Monitor connects to your tenant through the official Microsoft APIs and:

* **Continuously monitors** capacity consumption (in Capacity Units), semantic model refreshes, runs of pipelines, notebooks, Copy jobs, and Dataflows Gen2, data gateways, and Fabric Mirroring;
* **Sends alerts** by email, Microsoft Teams, Slack, and Telegram when it detects failures, offline gateways, capacities close to their limit, or unusual consumption, and notifies you when the problem has been resolved;
* **Centralizes the tenant inventory**: workspaces, reports, semantic models, dataflows, lakehouses, warehouses, notebooks, pipelines, capacities, gateways, connections, and other Fabric items;
* **Helps control capacity costs**, with cost per capacity, scheduled pause and resume, scaling, and Auto-Scale;
* **Assesses the quality** of semantic models (best practices, AI readiness, lineage, data dictionary, data exposure);
* **Audits** activities, report views, and access permissions.

### Why use Power Monitor?

Without proactive monitoring, Power BI and Fabric administrators are stuck in **reactive mode**. Power Monitor reverses this logic: your team knows about the problem **before** the user does and has the data to act.

To learn more, see [What is Power Monitor](/en/readme/o-que-e-o-power-monitor.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/perguntas-frequentes/duvidas-gerais/o-que-e-o-power-monitor.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.