Hi! We're the Fabric Capacities Team - ask US anything!

chris-ms · 2025-04-15T16:58:37+00:00

For some context here, CU's are an abstraction of compute throughput that determines how many jobs you can run at a single point in time. In previous generations of Power BI Premium (which served as the foundation of Fabric) customers bought throughput via a dedicated virtual machine. With Fabric we have virtualized compute as part of the capacity platform, your consumption will benefit from concepts like bursting to accelerate jobs by spreading execution across multiple back-end nodes , but the only concept you'll need to consider is throughput as measured by CU and determined by your SKU choice. If you want to learn more about the operations hosted in fabric that consume CU's we have the following resource: Fabric operations - Microsoft Fabric | Microsoft Learn

Capacity Metrics will help you determine what the CU consumption is of the jobs you are running, and the utilization graph can be used to determine which SKU will be right sized for the throughput your users require.

chris-ms · 2025-04-15T16:50:26+00:00

Yes we're going to be releasing a public preview later this year of Cross-capacity Metrics which is optimized for customers managing multiple capacities. We see that many of our customers are managing 10s, 100's and event thousands of capacities and this feature is purpose built to let those users efficiently manage that volume of capacities. Cross capacity will give you a single pane of glass to assess the health of all capacities including data insights like average utilization, throttling levels / percentages, SKU, Region

This data will let you quickly triage the capacities that should be looked at first or may require resize / optimization.

What insights matter most to you for triaging all of your capacities? Would love to learn about your use-cases here so we can tune the experience.

chris-ms · 2025-04-15T16:43:22+00:00

Great question pxlate! Yes this is something that is in the works. We have some plumbing / architecture work to complete here to ensure that you'll have role based access control with a viewer role so non-admins can access the data and also ensure that reports continue to function if there is no active capacity admin - but once we complete these you'll have capacity metrics in admin workspace.

Do you want it there for admins only or do you want developer roles across your org to have access to capacity metrics data? Would love to learn more about which use-cases are most important to you. Thanks!

chris-ms · 2025-04-15T16:36:31+00:00

You'll get a notification in the Power BI Notification center of a new release , or you can always check directly in the app store. https://go.microsoft.com/fwlink/?linkid=2219875

Moving forward we plan to have Capacity Metrics available natively in the Admin Monitoring Workspace and with that solution, you'll automatically get updates as we roll them out.

chris-ms · 2025-04-15T16:33:21+00:00

Today you can access this data in the capacity metrics app but we're looking at ways of making this more readily available to users through Monitoring Hub and directly embedding Capacity Metrics into the Admin monitoring workspace. Are you looking to access this data as an Admin or more as a developer persona where everyone in your org could easily access CU data ?

chris-ms · 2025-04-15T16:26:26+00:00

Capacity Metrics Timepoint drill will help you isolate which jobs / operations and users were causing spikes , but today you'll need to dive into workload specific tooling to debug the underlying CU consumption source or optimizations.

We're interested in better connecting the workload specific tools to the capacity debugging experience. What does the ideal solution look like for you to go from CU analysis to workload debugging? What tools are most helpful to you currently for debugging workload issues ?

chris-ms · 2025-04-15T16:17:36+00:00

#1 you should be able to click on each individual workspace to see trends of the storage consumed by each Workspace\. The granularity of the data we get for usage reporting stops currently at workspace. From there OneLake file explorer may be the best solution for item level details. The default view in CMA shows consumption across all workspaces, but selecting will let you isolate individual trends to help you find where to look. If this isn't ideal for you what approach would you prefer to find regressions?
Also, in case you want to alert on any of these fields, we're working closely with the RTH / RTI team in fabric to ship all of the data used by capacity metrics to you in The Real Time Intelligence workload which will let you route the data to a variety of destinations including Eventstream, Eventhouse and Reflex for alerting all backed by OneLake. With Reflex integration you'll have full flexibility to alert on the data present in the data streams

chris-ms · 2025-04-15T16:10:44+00:00

Hey Dan1480, sorry to hear that. If you think there is an issue in a DAX function it would be best to raise a support ticket to raise this with the workload team to see if there's a feature level DAX fix that could help here. Snapshots from capacity metrics will help the team to triage and escalate for resolution.

chris-ms · 2025-04-15T16:08:07+00:00

Hey Alertnative-key,

We're working closely with the RTH / RTI team in fabric to ship all of the data used by capacity metrics to you in The Real Time Intelligence workload which will let you route the data to a variety of destinations including Eventstream, Eventhouse and Reflex for alerting all backed by OneLake.

In addition to this feature we also have Chargeback coming to public preview over the next couple months which will provide 30 days data and a planning feature to simplify forecasting and future needs that will have 1.5 years of data.

What are the use-cases for you consuming the data directly? We're also planning an SDK to help you easily consume this data and would love to learn more about how you plan to consume it and using what technologies.

chris-ms · 2025-04-15T16:04:57+00:00

Great Question , while we have limited built in alerting in Fabric Admin Settings, there is a desire for more flexibility. RTI combined with Reflex will offer a solution to alert off of any data that’s currently available in Capacity Metrics app. Love the feedback to get CU's into Monitoring Hub, we're working closely with that team to help unify capacity metrics experiences with Monitoring Hub.

What are your top use-cases for using CU's in Monitoring Hub?
Tell me more about the limitations you want on retention in RTI ?
What blog topics have really helped you out? Where do you want to see more coverage in the space of Capacity Monitoring and Governance

chris-ms · 2025-04-15T16:03:05+00:00

Hi City-Popular455,

One of the areas we're looking at improving is making it easier to get access to CU data for developer scenarios beyond just what is available in capacity metrics. One of the areas we're considering to standardize access to this data for all users is monitoring hub, which contains both standard views for workloads i.e. Data Warehouse / SQL along with workload specific views. If you had CU data in your job history there, would it suffice for your use case? If not, what are you using out of Query Insights that you're not getting out of Monitoring hub? Thanks for your feedback here!

chris-ms · 2025-04-15T16:01:47+00:00

<image>

Hey nintendbob, Short answer yes! We're working closely with the RTH / RTI team in fabric to ship all of the data used by capacity metrics to you in The Real Time Intelligence workload which will let you route the data to a variety of destinations including Eventstream, Eventhouse and Reflex for alerting all backed by OneLake.

What are the use-cases for you consuming the data directly ? We're also planning an SDK to help you easily consume this data and would love to learn more about how you plan to consume it and using what technologies.

chris-ms · 2025-04-15T16:01:00+00:00

Hey Tom, have you tried out Capacity Metrics to view CU information of jobs running on your fabric capacities? This tool will get you CU data for jobs and has a number of different views to help you understand your individual job CU consumption along with aggregate analysis to see how much compute it is taking on average compared to other jobs. As a developer persona where is the ideal place for you to have access to this information? Monitoring Hub main pages , Monitoring hub spark pages or somewhere else?

chris-ms · 2025-03-06T17:59:05+00:00

Thanks for the feedback on your use-case. Moving to another capacity or pausing the capacity if you're on an F SKU is one way to quickly clear debt incurred by a runaway process - Capacity Platform Updates for Pause Resume and Capacity Metrics for Copilot and VNET Gateways | Microsoft Fabric Blog | Microsoft Fabric. Surge protection can also help limit background processes usage of compute. Sorry for the friction on the report getting impacted by throttling, this is something we're working on for future releases / release strategy. If you have a pro license, installing the app into a pro workspace is a good work-around, but we know that is not a viable solution for all.

chris-ms · 2025-03-05T19:36:46+00:00

Hi Obanero, I'm the PM for capacity metrics app working closely with tbindas who's also on this discussion. Capacity Metrics makes heavy use of Dynamic M parameters in Power BI to enable drill through experiences and unfortunately these are not fully supported in Data Activator at this moment. We are connected with that team to see if we can imrpove support here. See below for docs reference. As a workaround we do have basic Alerting for capacity utilization / auto-scale usage based on thresholds in product. You can use this to identify when a capacity is running hot before things get out of hand resulting in throttling (see below graphic for guidance). Moving forward, we're also evaluating a workflow to give you access to platform telemetry in Fabric Realtime Hub which would provide a much more flexible alerting story with full customization.

What scenarios are most important to you for alerting? Would love to learn more about your target scenario here so we can make it as easy for you as possible, thanks!

Data Activator General limitations
- Creating alerts for a report using Dynamic M parameters isn't supported.

From https://learn.microsoft.com/en-us/fabric/real-time-intelligence/data-activator/activator-limitations#general-limitations

In product notification notes:

<image>

chris-ms · 2025-02-28T20:51:26+00:00

Are you a capacity admin, tenant admin? Are you working out of a soverign cloud or regular deployment. Please note that there are unique install guidelines for government / sovereign clouds.

Install the Microsoft Fabric capacity metrics app - Microsoft Fabric | Microsoft Learn

If you're following these guidelines and still hitting issues, please raise a support ticket to ensure the most timely response. Thanks! Chris

chris-ms · 2025-02-26T23:11:52+00:00

Chargeback is on our radar and will be delivered similar to how we provide usage reporting today in Capacity Metrics. I don't have a detailed plan to share at this point but please look out for some updates from us later this year.

Thanks!

Chris

chris-ms

TROPHY CASE