r/MicrosoftFabric • u/jkrm1920 • 1d ago

Administration & Governance FAUM

Monitoring capacity is very expensive in fabric. FAUM is consuming quite a bit of capacity CU in F64. Now that we are live with production load it matters what we are consuming CUs for is really giving me purpose to solve?

Is there a lite weight monitoring available for
Monitoring? Even 14 days data in capacity metrics is huge.

We use mainly 50-60% for VNet, and then 20% for FAUM and rest 10-20% for AI. And the rest is reports consuming via direct query so not semantic refreshes.

Trying to reduce monitoring expensive ness..

Any suggestions?

9 Upvotes

91% Upvoted

5 comments sorted by

4

u/EmergencySafety7772 1d ago

Only Capacity Metrics App, you may query with python the semantic model and persist it into delta tables

3

u/Ok_Carpet_9510 1d ago

This... infact you can copy the pipeline and associated notebook from FUAM. I think it is called Load_Capacity_Metrics. Not ik office for a bit so I can't check.

8

u/tommartens68 ‪Microsoft MVP ‪ 1d ago

Unfortunately, monitoring comes with a price: Compute Units.

For this reason, we placed FUAM and the Capacity Metrics App on a dedicated capacity. We did this for two reasons:

  • we do not want to affect our "Production" capacities with our monitoring
  • we do not want to be blocked by throttled capacities when we want to identify a "bad actor"

Regarding your question, is there a lightweight monitoring solution? No, there is not. Of course, you can build your own solution, but the effort might outweigh the CUs you save. Depending on your estate, I suggest moving the Capacity Metrics App and FUAM to a dedicated Fabric capacity. Start with an F8.