Reporting on Concurrent Operations in Fabric

[dmbd1904]

Different capacity licensing options within Fabric allow different volumes of concurrent operations. We are having issues with this limitation, but how can I monitor the number of concurrently running operations at any one time? The Capacity Monitoring / Metrics app doesn't make this easy to understand

[dmbd1904]

Hi I'm referring to concurrent jobs, as documented here Concurrency limits and queueing for Fabric Spark - Microsoft Fabric | Microsoft Learn. I'm using 'refresh' as an umbrella term for the executing / running of artifacts in Fabric (E.g. Notebooks, Pipelines, Datasets etc)

[lbendlin]

so CUs basically.  This might help 

Fabric Capacities – Everything you need to know about what’s new and what’s coming | Microsoft Fabri...

[dmbd1904]

Thank you. Since reviewing the link I've noticed that our client still has v1 of the monitoring app installed and so we don't have the full range of metrics referred to in the link. Will get the app updated and see if this sheds any light on our issues.

[lbendlin]

you may also want to review the recently posted presentations on Fabric features and pricing, especially the part where they talk about costing and smoothing of CUs

Fabric PowerPoint Presentations Gallery - Microsoft Fabric Community

[lbendlin]

Not clear what your issue is. Are you experiencing CU starvation? 

[dmbd1904]

Hi I don't believe so. We are peaking at 60% CU Capacity within a client environment but have solution refreshes intermittently failing. The only reason I could suspet is the number of concurrent operations (Which I want to monitor, but don't know how to in the capacity monitoring app). Even so, I don't know why refreshes are failing when jobs should be auto queued for min. 24 hours

[lbendlin]

I have never heard the concept of "concurrent operations"  mentioned in any discussions we had with Microsoft. For Gen 1 we were talking renderers, now with Gen 2 we are talking CUs.  When you say "solution refresh"  what do you mean?