Forum Discussion
One Lake Capacity Consumption
Hi smpa01
As of now, the Fabric Capacity Metrics app is where you can monitor the capacity consumption. It requires that you must be a capacity admin to install and view this app.
The operations of transactions are classified into five categories, regardless of the source and destination of their reads and writes, when the requests are sent to OneLake. If you read data from external server into a Fabric item in OneLake, this will consume your Fabric capacity.
The app provides a page to help analyze which operations and users contributed the most to your capacity's usage over a timerange. It provides more details like workspace, user, item, operation, duration, status .etc. Maybe we can analyze the data to know which operation consumes less capacity. However, it is difficult to predict in advance that one operation will necessarily consume less capacity than others.
These documents may provide helpful insights:
OneLake consumption - Microsoft Fabric | Microsoft Learn
Map each REST operation to a price - Azure Blob Storage | Microsoft Learn
Understand the metrics app compute page - Microsoft Fabric | Microsoft Learn
Understand the metrics app timepoint page - Microsoft Fabric | Microsoft Learn
Best Regards,
Jing
If this post helps, please Accept it as Solution to help other members find it. Appreciate your Kudos!
Anonymous than you for this.
I came across this. As per this Redirect is safer the proxy.
Can you please elaborate how can I ensure that all my Read, Write operations follow Redirect and not proxy.
A typical case will be bulk ingestion of tables (upsert) from external data-vendor through on-prem server, transformation, machine-learning + exploratory anaalysis and reporting back to end users through power bi.
Is there a chart/doc exists somewhere that clearly shows Redirect vs proxy by Read and write and by agents avaialable (df gen1, df gen2, notebook, pipeline etc). Also, is there any way for the developer to know either through Monitot or any other API whether the operation results in Redirect/proxy? This is a blocker currently.
Also, since it is a global account, the workspace level admins will never be give access to that. How can we get exposure to those valuable piece of information without relying on the app.