Forum Discussion
Power BI Fabric Capacity Monitoring: Linking CU Consumption to Specific Reports
Hi SCUTARI_Santiag ,
As per Microsoft Fabric Capacity Metrics app: This is the official and most comprehensive tool for monitoring your Fabric capacity consumption. so basically it Identify top CU consumers (items and operations) as shown in image.
for Optimizing Reports there are lot of factor but i highlights some of like:-,
- Streamline your data model by importing only necessary data and optimizing data types.
- Prefer DAX measures over calculated columns to reduce model size and improve refresh times.
- Optimize visuals and report layout by limiting visuals per page and choosing efficient visual types.
- Implement strategic data refresh practices like incremental refresh and smart scheduling.
- Utilize performance monitoring tools such as Power BI Performance Analyzer, DAX Studio, and Tabular Editor.
Super UserYou're not alone in facing this challenge—many organizations using Power BI Fabric encounter the same limitation when it comes to granular capacity monitoring, especially in environments with heavy reliance on shared semantic models. The Fabric Capacity Metrics app provides insights primarily at the semantic model level, which is helpful for broad analysis, but insufficient for pinpointing which specific reports are driving high Capacity Unit (CU) consumption. This lack of granularity makes it difficult to diagnose performance bottlenecks or optimize individual report usage.
Unfortunately, Power BI currently does not offer a built-in or direct method to track CU consumption per report within a semantic model. However, there are some recommended practices and workarounds you can consider to bridge this gap:
-
Power BI Activity Log + Query Logs: By combining the Power BI Activity Log (which captures user-level actions like report views and dataset queries) with the XMLA query logs or Query Diagnostics from Premium workspaces, you can correlate the frequency and intensity of report usage. While this won't directly translate to CUs, it gives you a proxy to identify which reports are likely contributing most to semantic model load.
-
Log Analytics Integration: If you're using Microsoft Purview or enabling Azure Monitor / Log Analytics integration with your Fabric capacity, you can collect query-level telemetry and refresh performance data, allowing deeper exploration of which reports or users are generating heavy queries.
-
Custom Telemetry: Implement telemetry in your reports using Power BI usage metrics, custom audit logging (e.g., through Power Automate flows that track report opens), or usage tagging techniques (such as embedding report metadata or unique user/session info in query parameters). You can then analyze usage patterns alongside CU data to approximate report-level impact.
-
Segment Shared Models: For very high-traffic semantic models, consider creating segmented versions (by business unit, report group, or department) to isolate CU usage and monitor more cleanly at a smaller scale.
-
Feature Requests and Feedback Loop: Microsoft is aware of this limitation, and you can submit or vote for this feature through the Power BI Ideas portal to push for per-report CU monitoring in future updates.
In summary, while direct report-level CU tracking is not natively available today, combining Activity Logs, Log Analytics, and smart usage telemetry can give you a reasonable level of insight. It's an area where careful architecture (e.g., segmenting shared models) and monitoring strategy can significantly improve visibility and capacity planning.