Forum Discussion
Fabric Capacity Metrics
I'm trying to wrap my head around the Fabric Capacity Metrics app for monitoring performance. What are the key metrics you check first when troubleshooting a slow report or Dataset refresh?
Start by analyzing CU utilization in the Capacity Metrics app, focusing on the Timepoint Summary or Detail views. Identify which workspace, item, and operation are contributing to the spike. This will help you quickly narrow down the source and understand the reason behind increased CU consumption. Given below sample reference that indicates one of the data movement causing CU utilization.
For performance-related issues, you can also use the Monitoring (Monitor) app to check the execution duration of Fabric items such as pipelines, notebooks, or dataflows. This provides additional insights into where time is being spent during execution and helps pinpoint bottlenecks.
Sanyukti_Jain
Hi,
In fabric capacity metrics app, you can check the following KPI's
1-CU(CapacityUnit) Consumption:
2-Thortlling and delays
3-Identify Top Consumers
4-Refresh Duration and resource Usage
You may export or download the report and analyze these metrics for perfromance related issues.
Screen shot attached below for your reference or for complete detail, please refer to microsoft documentation link.
https://learn.microsoft.com/en-us/fabric/enterprise/metrics-appIf this helps, ✓ Mark as Kudos | Help Others
5 Replies
Sanyukti_Jain
Hi,
In fabric capacity metrics app, you can check the following KPI's
1-CU(CapacityUnit) Consumption:
2-Thortlling and delays
3-Identify Top Consumers
4-Refresh Duration and resource Usage
You may export or download the report and analyze these metrics for perfromance related issues.
Screen shot attached below for your reference or for complete detail, please refer to microsoft documentation link.
https://learn.microsoft.com/en-us/fabric/enterprise/metrics-appIf this helps, ✓ Mark as Kudos | Help Others
Start by analyzing CU utilization in the Capacity Metrics app, focusing on the Timepoint Summary or Detail views. Identify which workspace, item, and operation are contributing to the spike. This will help you quickly narrow down the source and understand the reason behind increased CU consumption. Given below sample reference that indicates one of the data movement causing CU utilization.
For performance-related issues, you can also use the Monitoring (Monitor) app to check the execution duration of Fabric items such as pipelines, notebooks, or dataflows. This provides additional insights into where time is being spent during execution and helps pinpoint bottlenecks.
I always look at the interactive and background processes first to make sure that the combination of these are not over 100%, because if they're over 100% there would be some throttling happening. If it is over 100% you can then drill through to the time point detail to see what has caused that to go over 100%, which then allow you to troubleshoot further.
Thank you for submitting your question to the Microsoft Fabric Community Forum, and thanks to BalajiL , GilbertQ and Murtaza_Ghafoor for sharing helpful suggestions.
Could you let us know if the suggested solution resolved your issue? If not, please share any additional details so we can assist further.
Best regards,
Community Support TeamHi Sanyukti_Jain
Just checking as we haven't received a response to our previous message. Were you able to review the information above? Let us know if you have any additional questions.Regards,
Microsoft Fabric Community Support Team.
