> 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.md).

# What is Managed Monitoring?

Learn how the Power Tuning team can act proactively, 24/7, on the critical alerts of your Fabric and Power BI environment, with Power Monitor included.

**Managed Monitoring** is an **optional service** from Power Tuning, delivered by people: our team of Microsoft Fabric and Power BI specialists follows the **critical alerts** generated by Power Monitor in your environment, **24 hours a day, 7 days a week**.

When a critical alert is received, **our team acts**: it assesses the impact, communicates with the parties involved, and starts analyzing and fixing the problem, always with your approval before consuming action hours.

{% hint style="info" %}
**Power Monitor is included** in the Managed Monitoring plans, with no additional cost for the tool.
{% endhint %}

{% hint style="warning" %}
Managed Monitoring **is not a software feature**: it is contracted separately, directly with Power Tuning. The Power Monitor platform works normally without it, with alerts reaching your own team.
{% endhint %}

***

### Who is this service for?

Managed Monitoring is ideal for companies that:

* do not have an internal team specialized in Fabric/Power BI available 24/7;
* need a **first-response SLA** for critical incidents;
* want to **leave reactive mode** and have specialists acting before problems affect users;
* have critical environments, where data unavailability directly impacts the business.

***

### What is included?

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>What is covered</strong></td><td>Monitoring scope and what is left out</td><td><a href="/en/managed-monitoring/monitoramento-gerenciado/o-que-esta-coberto.md">What is covered</a></td></tr><tr><td><strong>Available plans</strong></td><td>Essential, Professional, and Enterprise</td><td><a href="/en/managed-monitoring/monitoramento-gerenciado/planos.md">Available plans</a></td></tr><tr><td><strong>Hours model</strong></td><td>How action hours on problems work</td><td><a href="/en/managed-monitoring/monitoramento-gerenciado/horas-de-atuacao.md">Remediation hours model</a></td></tr><tr><td><strong>SLA and support</strong></td><td>Response time and how support works</td><td><a href="/en/managed-monitoring/monitoramento-gerenciado/sla.md">SLA and support</a></td></tr></tbody></table>

***

### Request a proposal

To receive a customized proposal for the size of your environment:

* [Talk to a specialist on WhatsApp](https://powermonitor.com.br/whatsapp)
* [Schedule a presentation](https://powermonitor.com.br/apresentacao)
* [Start a free Power Monitor trial](https://powermonitor.com.br/instalacao)


---

# 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.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.