> 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/managed-monitoring/monitoramento-gerenciado/o-que-esta-coberto.md).

# What is covered

Which alerts the Managed Monitoring team handles and which requests are out of scope.

Managed Monitoring covers the **critical infrastructure alerts** detected by Power Monitor, related to the operation of Power BI and Microsoft Fabric.

### What is covered

When a critical alert from Power Monitor is received, our team acts to investigate, communicate, and resolve it:

| Situation (Power Monitor alert)                          | Team action                                                                  |
| -------------------------------------------------------- | ---------------------------------------------------------------------------- |
| **Gateway offline or failing**                           | Diagnosis, communication to the customer, and action to restore connectivity |
| **Data refresh failure** (semantic models and dataflows) | Identification of the root cause and action to normalize ingestion           |
| **Notebook and pipeline run failure**                    | Diagnosis of recurring errors and critical processing failures               |
| **Capacity close to or at the limit**                    | Analysis of the workloads consuming the capacity and action to avoid impact  |
| **Capacity unexpectedly turned off or suspended**        | Action to restore the capacity and identify the cause                        |
| **Other critical infrastructure alerts**                 | Any other critical alert detected by Power Monitor that requires attention   |

The alert types available in Power Monitor are described in [Real-time alerts](/en/principais-funcionalidades/alertas-em-tempo-real.md).

***

### What is **not** covered

Managed Monitoring covers infrastructure, **not development**. The following are out of scope:

* Incorrect data errors in reports
* Improvements and enhancements to existing reports
* Creation of new reports or dashboards
* Query performance optimization (DAX, SQL, M)
* Capacity consumption reduction through optimization
* Development of pipelines, Data Warehouse, or Lakehouse
* DevOps and CI/CD implementation

{% hint style="info" %}
These situations may **generate alerts** in Power Monitor, but their resolution involves development and is not covered by Managed Monitoring. They can be contracted separately with Power Tuning.
{% endhint %}

***

### Can I contract development separately?

Yes. Power Tuning offers complementary services for the development and evolution needs of your environment:

* **One-off projects:** specific needs, with fixed scope and deadline;
* **Monthly development support:** hours bank for ongoing requests involving Power BI reports, DAX, M, pipelines, Lakehouse, Data Warehouse, DevOps, and CI/CD;
* **Report optimization:** reduction of Fabric capacity consumption and improvement of visual and semantic model performance.

[Talk to our team about development](https://powermonitor.com.br/whatsapp)


---

# 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/managed-monitoring/monitoramento-gerenciado/o-que-esta-coberto.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.