> 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-gerais/o-que-e-um-artefato.md).

# What is an artifact?

What Power Monitor calls an artifact (item) and how these items are inventoried and counted.

An **artifact** (or **item**) is any Power BI or Microsoft Fabric content item located **inside a workspace**: a report, a semantic model, a dataflow, a notebook, a pipeline, a lakehouse, and so on.

The artifact count serves two purposes:

* **Inventory and monitoring:** artifacts appear on the Governance, Monitoring, and Data Quality screens;
* **Billing:** the number of artifacts in **monitored workspaces** determines the monthly fee tier.

### What item types exist?

Power Monitor inventories **34 item types**, including:

| Area                | Examples                                                                                       |
| ------------------- | ---------------------------------------------------------------------------------------------- |
| Power BI            | Reports (including paginated), semantic models, dashboards, dataflows, datamarts               |
| Storage             | Lakehouses, warehouses, SQL databases, mirrored databases, KQL databases, eventhouses          |
| Data engineering    | Notebooks, data pipelines, Copy jobs, Spark job definitions, Apache Airflow jobs, environments |
| Data science and AI | ML models, ML experiments, Data agents                                                         |
| Real-time           | Eventstreams, KQL dashboards, KQL querysets, Activator (Reflex)                                |

The full list is in [What counts as an artifact for pricing purposes?](/en/perguntas-frequentes/licenciamento/o-que-e-contado-como-artefato.md)

### Are workspaces, capacities, and gateways artifacts?

No. **Workspaces**, **capacities**, **gateways**, and **connections** are inventoried and monitored by Power Monitor, but they **do not count** as artifacts for billing.

### How does Power Monitor count artifacts?

* The inventory is updated by **automatic daily scans** (and by on-demand scans run by administrators in **Mapping**).
* For billing, the quantity is recorded **once a day** and the month's tier is determined by the **average of the measured days**.
* Items deleted in the tenant stop being counted starting on the day the deletion is detected and appear on the **Governance › Operations › Deleted Artifacts** screen.

### Are paginated reports counted?

Yes. Paginated reports are reports and are included in the count.

### Are artifacts in personal workspaces counted?

No. Power Monitor inventories only **collaborative workspaces**. Each user's "My workspace" is not included.

### What happens if the number of artifacts changes?

Nothing needs to be done: the tier is adjusted automatically by the month's average. See [How much does Power Monitor cost?](/en/readme/quanto-custa-o-power-monitor.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-gerais/o-que-e-um-artefato.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.