Hi Fabric Capacity Team, I would like to bring to your attention an enhancement opportunity within the Microsoft Fabric Capacity Metrics app that can significantly improve our monitoring, governance, and cost optimization capabilities. Current Limitation: At present, the Capacity Metrics app provides insights at the workspace and workload level. However, it lacks visibility into item-level capacity consumption, making it difficult to identify which specific artifacts such as reports, semantic models, pipelines, or notebooks are driving resource utilization. Key Challenges: Limited ability to perform root cause analysis for capacity spikes Difficulty in identifying top resource-consuming items Constraints in optimizing capacity usage and associated costs Reduced effectiveness in governance and performance monitoring Proposed Enhancement: We propose introducing granular, item-level capacity insights with the following capabilities: Detailed consumption breakdown by individual items (reports, datasets, pipelines, notebooks, etc.) Time-based granularity, such as hourly or near real-time tracking Top-N analysis to identify high-consuming items within a selected timeframe (e.g., top 5 items in the last hour) Advanced filtering by workspace, item type, and capacity Data export and API access for extended analysis and integration Expected Benefits: Improved cost optimization through better visibility of high-usage items Faster and more accurate troubleshooting of capacity-related issues Enhanced governance and monitoring across workspaces Data-driven decision-making for capacity planning and performance tuning Considering Fabric’s internal mechanisms such as smoothing and bursting, having granular visibility will further help in understanding actual consumption patterns and enable more effective optimization strategies. I recommend that we formally submit this enhancement request through the Fabric Ideas portal to ensure it is considered in future roadmap discussions. Please let me know your thoughts or if you would like to discuss this further. Regards, Jayasudha Mudaliar
... View more