> 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/es/documentacion-tecnica/documentacao-tecnica/arquitetura.md).

# Arquitectura

Arquitectura técnica del Power Monitor, para los equipos de TI, arquitectura y seguridad de los clientes.

Esta sección describe la arquitectura técnica del Power Monitor: cómo se organizan los componentes de la plataforma, cómo se recopilan los datos de su tenant, cómo funciona el monitoreo continuo y qué información se almacena.

> Esta documentación está dirigida a los equipos de TI, arquitectura y seguridad que necesitan evaluar o comprender el funcionamiento de la plataforma. Para el uso diario, consulte la sección **Power Monitor**.

<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>Visión general</strong></td><td>Componentes, tecnologías, multi-tenancy y seguridad</td><td><a href="/es/documentacion-tecnica/documentacao-tecnica/visao-geral.md">Visión general</a></td></tr><tr><td><strong>Flujo de escaneos</strong></td><td>Cómo se recopila el inventario de Power BI / Fabric</td><td><a href="/es/documentacion-tecnica/documentacao-tecnica/fluxo-de-scans.md">Flujo de escaneos</a></td></tr><tr><td><strong>Monitoreo continuo</strong></td><td>Cómo el sistema detecta fallas y envía alertas</td><td><a href="/es/documentacion-tecnica/documentacao-tecnica/monitoramento-continuo.md">Monitoreo continuo</a></td></tr><tr><td><strong>Modelo de datos</strong></td><td>Principales entidades y artefactos rastreados</td><td><a href="/es/documentacion-tecnica/documentacao-tecnica/modelo-de-dados.md">Modelo de datos</a></td></tr></tbody></table>


---

# 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/es/documentacion-tecnica/documentacao-tecnica/arquitetura.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.