> 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-tecnicas/quais-artefatos-sao-monitorados.md). # Which artifacts are monitored? What Power Monitor inventories and what it actively monitors, with alerts, in your Fabric and Power BI environment. Power Monitor does two different things with the items in your tenant: * **Inventory (governance):** lists and details all items in the monitored workspaces, with metadata, owner, capacity, lineage, and permissions; * **Active monitoring (with alerts):** continuously tracks what can fail or consume too much. ### Active monitoring | Resource | What is tracked | Alerts | | -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | Fabric (F), Premium (P), and Embedded (A) **capacities** | Consumption in Capacity Units (interactive, background, and accumulated usage), from the Fabric Capacity Metrics app; history, comparisons, and anomalies by item; daily cost (with the Azure permission) | Usage limit (80%), background usage, consumption data unavailable, consumption anomaly by item, cost above average, capacity running outside business hours | | **Data gateways** | Status (online/offline) of each gateway on which the Power Monitor application is an administrator | Gateway offline and resolution | | **Semantic models** on capacity | Refresh history, failures with error code and message, duration | Refresh failure; execution time deviation (optional, per item) | | **Fabric items**: data pipelines, notebooks, Copy jobs, and Dataflows Gen2 | Runs, status, and duration | Fabric item failure (failure or cancellation); execution time deviation (optional) | | **Dataflows Gen1** | Run duration | Execution time deviation (optional) | | **Data Freshness** | Data delay in tables you choose (most recent date/time of a column) | Delayed data | | **Fabric Mirroring** | Mirroring state of mirrored databases | Mirroring issues | {% hint style="info" %} Today Power Monitor does **not** monitor refresh failures of paginated reports or Dataflows Gen1, nor does it detect runs stuck due to timeout. Spark job definitions appear in the inventory, but their runs are not monitored. {% endhint %} ### Inventory The inventory covers **34 item types** within workspaces, in addition to tenant-level resources: * **Workspaces**, with capacity, domain, administrators, and governance metadata; * **Reports** (including paginated), dashboards, apps, KQL dashboards, explorations, metric sets, and public links (publish to web); * **Semantic models**, with tables, columns, measures, data sources, size, and schedules; * **Storage**: lakehouses, warehouses, SQL databases, mirrored databases, KQL databases, and eventhouses; * **Data engineering and data science**: notebooks, pipelines, Copy jobs, Spark job definitions, Airflow jobs, environments, ML models, and ML experiments; * **Real-time**: eventstreams, Activator, and KQL querysets; * **Capacities, gateways, connections, and domains**; * **Deleted artifacts** in the tenant, with the date the deletion was detected. ### Quality, permissions, and audit * **Data Quality:** lineage, data dictionary, Best Practices Score (55 rules), AI Score (model readiness for Copilot and natural language), X-Ray, data exposure, and model cleanup (columns, tables, and measures not used by reports). * **Permissions:** audit of all permissions on workspaces, items, connections, and gateways, with expansion of Entra ID groups and identification of external accounts. * **Audit:** tenant activity events and report views (who viewed what, when, and from where), when collection is enabled. * **Performance Assessment** (beta): on-demand analysis of a semantic model (VertiPaq structure, Power Query, best practices, unused columns, and capacity consumption), with recommendations. See also [What counts as an artifact for pricing purposes?](/en/perguntas-frequentes/licenciamento/o-que-e-contado-como-artefato.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-tecnicas/quais-artefatos-sao-monitorados.md?ask=&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.