> 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/licenciamento/o-que-e-contado-como-artefato.md). # What counts as an artifact for pricing purposes? Which Power BI and Microsoft Fabric items are included in the count that determines the Power Monitor monthly fee tier. The Power Monitor monthly fee is determined by the number of **monitored items (artifacts)**: the content items located **inside monitored workspaces**. The count is done automatically, once a day. ### What counts **34 item types** from Power BI and Microsoft Fabric are counted: | Area | Item types counted | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | **Power BI** | Reports (including paginated reports), semantic models, dashboards, dataflows, datamarts | | **Data storage** | Lakehouses, warehouses, SQL databases, mirrored databases (Mirroring), KQL databases, eventhouses | | **Data engineering** | Notebooks, data pipelines, Copy jobs, Spark job definitions, Apache Airflow jobs, dbt jobs, environments, User data functions, Variable libraries | | **Data science and AI** | ML models, ML experiments, Data agents | | **Real-time** | Eventstreams, KQL dashboards, KQL querysets, Activator (Reflex), event subscriptions | | **Other Fabric items** | Explorations, Metric sets, Org apps, Ontologies, Graph models, App backends | ### What does NOT count | Item | Counts? | | --------------------------------------------- | -------------------------------------------------- | | Workspaces | ❌ No | | Capacities (Fabric, Premium, Embedded) | ❌ No | | Data gateways | ❌ No | | Connections and data sources | ❌ No | | Power BI apps (apps published to audiences) | ❌ No | | Power Monitor users | ❌ No | | Items in **unmonitored** workspaces | ❌ No | | Items in "My workspace" (personal workspaces) | ❌ No, they are not inventoried | | Items deleted in the tenant | ❌ No, starting on the day the deletion is detected | {% hint style="info" %} Capacities, gateways, and connections **are monitored normally**. They are just not included in the monthly fee calculation base. {% endhint %} ### Do inactive or unscheduled items count? Yes. If the item exists in a monitored workspace, it counts, whether or not it is being refreshed or accessed. To reduce the base, remove from monitoring the workspaces that do not need to be tracked, or delete from the tenant the items that are no longer used. The **Data Quality** and **Governance** screens help you find unused items. ### When does an item stop being counted? The count is a daily record (at around 00:30, Brasília time) made from that day's inventory. Only items that **exist** in **monitored** workspaces are included. | Situation | When it stops counting | | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | You remove a workspace from monitoring | From the next daily record. The data already collected from the items is preserved, but they stop entering the count and stop being tracked by the scans while the workspace is unmonitored. | | An item is deleted in the tenant | After an inventory scan detects the deletion (they run every day). From the first daily record afterwards, the item leaves the count. | | A workspace is deleted in the tenant | Likewise: after the scan detects the deletion, the workspace and its items leave the count. | The records of previous days are **not recalculated**: the change applies from the day it happens. The month's invoice uses the **average of the measured days** of the cycle (rounded down, not counting the free trial days), so removing a workspace in the middle of the month reduces the average in proportion to the days that remain. To check what was counted on each day, use the **Daily Audit** tab in **Billing** (administrators): the timeline shows the number of items per day and the **View Scan Items** action lists the counted items. ### How do I know how many items I have? * In **Billing** (administrators): the current quantity, the current tier, and the daily audit with the list of items counted on each day. * On the **Dashboard** and on the **Governance** screens: the inventory by item type. ### How do I choose which workspaces are monitored? During installation you choose between **Scan Everything** (all workspaces monitored) and **Select Workspaces**. Afterwards, the administrator adjusts the selection on the [Workspaces](/en/power-monitor/governanca/workspaces.md) screen. {% hint style="warning" %} With workspace selection enabled (the default), new workspaces discovered by the scans are added **outside** monitoring and do not increase the invoice. If an administrator turns off this selection to monitor everything, **all workspaces start counting immediately**. {% endhint %} For more information, see [What is an artifact?](/en/perguntas-frequentes/duvidas-gerais/o-que-e-um-artefato.md) and [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/licenciamento/o-que-e-contado-como-artefato.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.