Forum Discussion
Capacity Utilization Reporting by Entity
As a Power BI Administrator, I want to access weekly and monthly utilization data from the Fabric Capacity Metrics app, So that I can analyze how much percentage of shared capacity is consumed by each entity on a daily or weekly basis, enabling better resource planning and performance monitoring.
7 Replies
- Lodha_JaydeepSolution Sage
Hi ashishdhakate03,
Do you need the App metrices app downlaod to monitor the usage, Please follow the documentation below and download from the App source.
Hope this is what you need please consider as an accepted solution if helps or give some kudos.https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app-install?tabs=1st
- Bipin-LalaSolution Sage
Hi ashishdhakate03,
The Microsoft Fabric Capacity Metrics app is very useful for monitoring capacity consumption, but if the requirement is to retain daily/weekly/monthly historical data by workspace, item, or other entity, you may need to persist the metrics yourself.
A practical approach is described here:
https://data-marc.com/2025/07/30/your-metrics-your-rules-extracting-and-storing-fabric-admin-and-capacity-metrics-data-in-fabric/
The approach uses the Capacity Metrics semantic model together with a composite model and Fabric/Semantic Link to extract the metrics and store them in a Lakehouse. Once the data is persisted, you can build your own historical Power BI report over it.
A bit couple of caveats
This approach relies on the Microsoft-provided Capacity Metrics semantic model, so I'd treat it as a practical/community solution rather than a guaranteed long-term API contract. The underlying Microsoft model can change, which could require adjustments to the extraction process.
I'd also recommend storing the extracted data incrementally in your own Lakehouse rather than continually overwriting it, so you can build a proper historical dataset.
So, if your requirement is "I need more than the native Metrics app's historical window and want to analyse capacity consumption by entity over weeks/months", this is a very reasonable approach to investigate.
For an enterprise implementation, I'd also validate the security implications, capacity overhead of the extraction process, and the supportability of depending on the Capacity Metrics semantic model before putting it into production.
From this, you can report:
- Daily CU consumption by workspace/item
- Weekly and monthly trends
- Top capacity consumers
- Interactive vs background consumption
- CU consumption by item type
- % of total CU consumption attributable to each entity
- Capacity utilization trends over time
Let me know if this helps.
- rizalard0684Resolver III
Hey ashishdhakate03
If you wish to access fabric metric app, you can follow these steps:https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app-install?tabs=1st
If you wish to analyse weekly and monthly capacity utilisation data, you can read through this in detail:
https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app-compute-page
https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app-timepoint-page
hope this helps.
- GilbertQSuper User
There is an option now where you can use the fabric real time events to capture the capacity events as they are happening. Once that is done you can then assist this to a lake house table to store it for a longer time. Here are more details
https://learn.microsoft.com/en-us/fabric/real-time-hub/explore-fabric-capacity-overview-events
- v-csrikanthCommunity Support
We would like to inquire whether have you got the chance to check the solutions provided by GilbertQ ShivekMaharaj rizalard0684 Bipin-Lala users in community to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.
- ShivekMaharajImpactful Individual
Hi ashishdhakate03,
If by "entity" you mean a Fabric workspace or item, I would also look at the newer Microsoft Fabric Chargeback app.
It is designed specifically for shared-capacity allocation and shows what percentage of the capacity is consumed by each workspace, item, or domain, together with daily CU utilization and drill-through into individual workspaces/items. That maps quite closely to the percentage-based reporting you described.
For recent operational analysis, the Capacity Metrics app also now has an Item History page in preview. It provides a 30-day view with workspace/item filters, CU(s) by date, CU(s) by item, and % Compute.
One caution with building directly on the Capacity Metrics semantic model: Microsoft currently states that the semantic model behind the app is supported only for the reports supplied with the app, so I would not treat Semantic Link/composite-model access to it as a supported long-term reporting API.
So I would approach it as:
- Recent capacity monitoring: Capacity Metrics / Item History
- Percentage allocation by workspace/item/domain: Fabric Chargeback app
- Longer-term custom historical reporting: persist supported exported/collected usage data in your own store rather than depending on the Metrics app semantic model
The Chargeback app would probably be my first choice for the requirement you described. Hi ashishdhakate03,
Two things up front: the Fabric Capacity Metrics app only covers Fabric/Premium capacities (there's no equivalent for Pro shared capacity), and it only keeps a rolling ~14 days of data. Within that window, the items/ranking matrix gives you exactly what you want: each workspace and item's CU consumption, which you can read as a percentage of the capacity.
The limitation is history: because it's only ~14 days, true weekly-over-weekly and monthly trends aren't in the app by default. For that you'd either export on a schedule to build up your own history, or connect to the app's underlying semantic model and snapshot it into your own report (common for this, just note it's not an officially supported dataset so the structure can change).