Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

See when key Fabric features will launch and what’s already live, all in one place and always up to date. Explore the new Fabric roadmap

Reply
Markds
New Member

Fabric metric apps - questions

Hi, 

A question related to the Fabric Metric App: when I have a high percentage of background in the CU% graph, for example, 500%, what does that necessarily mean?

I only have this percentage when I stop the fabric capacity. What conclusions can I draw from that?

2 ACCEPTED SOLUTIONS
Anonymous
Not applicable

Hi @Markds ,

 

In the Fabric Metric App, the CU% graph displays the percentage of capacity units (CUs) consumed by different types of operations.

 

When you see a high percentage of background operations (for example, 500%), it indicates that a large number of CUs are used for background tasks. These tasks typically include back-end processes, such as data refreshes that are not directly triggered by user actions.

 

The fact that you only see such a high percentage when you stop fabric capacity indicates that these background operations consume a lot of resources when the system is not actively processing user requests. This could mean that your capacity is heavily utilized for maintenance or other automated processes during downtime.

 

If you want to know more please refer to the official documentation below:

Understand the metrics app compute page - Microsoft Fabric | Microsoft Learn

 

Best Regards,
Yang
Community Support Team

 

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

View solution in original post

frithjof_v
Super User
Super User

Perhaps this link directly answers your question:

 

https://learn.microsoft.com/en-us/fabric/enterprise/monitor-paused-capacity#why-is-my-capacity-spiki...

 

"To allow your capacity to perform at the highest level, its usage is smoothed over time. When you pause your capacity, the remaining cumulative overages and smoothed operations are executed. As a result, a spike appears in the Utilization visual.

 

The spike provides an indication that your capacity was paused. You can hover over the spike to view and see the state of the capacity in the tooltip."

View solution in original post

3 REPLIES 3
frithjof_v
Super User
Super User

Perhaps this link directly answers your question:

 

https://learn.microsoft.com/en-us/fabric/enterprise/monitor-paused-capacity#why-is-my-capacity-spiki...

 

"To allow your capacity to perform at the highest level, its usage is smoothed over time. When you pause your capacity, the remaining cumulative overages and smoothed operations are executed. As a result, a spike appears in the Utilization visual.

 

The spike provides an indication that your capacity was paused. You can hover over the spike to view and see the state of the capacity in the tooltip."

frithjof_v
Super User
Super User

Hi @Markds ,

 

I don't know the answer to your question, however I am curious what happens if we pause a capacity, and I'm wondering if the behaviour you experience is related to the below information:

 

The docs says "When you pause your capacity, the remaining cumulative overages and smoothed operations on your capacity are summed, and added to your Azure bill. You can monitor a paused capacity using the Microsoft Fabric Capacity Metrics app."

 

https://learn.microsoft.com/en-us/fabric/enterprise/pause-resume

 

I'm wondering if the high CU% you observe is caused by the summing up of overages and smoothing when you pause a capacity.

 

Do you notice any extra billing when you pause the capacity?

Anonymous
Not applicable

Hi @Markds ,

 

In the Fabric Metric App, the CU% graph displays the percentage of capacity units (CUs) consumed by different types of operations.

 

When you see a high percentage of background operations (for example, 500%), it indicates that a large number of CUs are used for background tasks. These tasks typically include back-end processes, such as data refreshes that are not directly triggered by user actions.

 

The fact that you only see such a high percentage when you stop fabric capacity indicates that these background operations consume a lot of resources when the system is not actively processing user requests. This could mean that your capacity is heavily utilized for maintenance or other automated processes during downtime.

 

If you want to know more please refer to the official documentation below:

Understand the metrics app compute page - Microsoft Fabric | Microsoft Learn

 

Best Regards,
Yang
Community Support Team

 

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

Helpful resources

Announcements
May FBC25 Carousel

Fabric Monthly Update - May 2025

Check out the May 2025 Fabric update to learn about new features.

May 2025 Monthly Update

Fabric Community Update - May 2025

Find out what's new and trending in the Fabric community.