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

# Gateway Monitoring

How Power Monitor checks the availability of data gateways and notifies you when a gateway goes offline.

Data gateways are critical components in environments that consume on-premises sources (SQL Server, Oracle, SAP, network files, etc.). When a gateway goes offline, **all refreshes** that depend on it fail. Power Monitor checks gateway status continuously and notifies you as soon as one goes down, and again when it comes back.

## How it works

* The status of each gateway is queried **every 5 minutes** through the Power BI APIs.
* **Online** is considered healthy; **offline** or **unreachable** opens an incident.
* When the incident is opened, the **Gateway Offline** alert is sent; when the gateway comes back, the **Alert Resolved** notice is sent.
* The check is performed **per gateway (cluster)**, not machine by machine.

{% hint style="warning" %}
**Prerequisites:**

* **Gateway Monitoring** must be turned on in **Settings › Monitoring**.
* Only gateways on which the **Power Monitor application is an administrator** are monitored. Microsoft does not offer an admin API that lists the status of all gateways in the tenant; that is why administrator access is required. A Power Monitor administrator who is also a gateway administrator can grant this access in **Settings › Additional Permissions › Gateways and connections**.

See [Enable Gateway Monitoring](/en/power-monitor/monitoramento/gateways/ativar-monitoramento-de-gateways.md).
{% endhint %}

## Screens

* **Monitoring › Gateways:** total gateways, how many are online and offline, open incidents, last check, last change and incident duration. The page refreshes automatically every 5 minutes.
* **Governance › Infrastructure › Gateways:** gateway inventory, with version, machine, department, contact and connections.
* **Mapping › Gateways:** refreshes the gateway inventory (administrators).

## Tips to ensure availability

* **Use a gateway cluster:** with several machines, the failure of one server does not bring down refreshes.
* **Monitor the gateway server** (CPU, disk, memory) with your infrastructure tools.
* **Keep the gateway up to date:** older versions may lose compatibility with the service.
* **Configure the recipients** of the Gateway Offline alert in **Settings › Notifications**.

## Related pages

* [Gateways](/en/power-monitor/monitoramento/gateways.md)
* [Gateways (Governance)](/en/power-monitor/governanca/infraestrutura/gateways.md)
* [Real-time alerts](/en/principais-funcionalidades/alertas-em-tempo-real.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-gateways.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.