Pillar C
Alternatives to the Capacity Metrics App for Long-Term History & Attribution
The Capacity Metrics app keeps only 14 days of compute history. An honest build-vs-buy of the alternatives: SemPy vault, FUAM, and SpendWeave Pro.
Topic
#monitoring
11 articles
Pillar C
Extract Fabric Capacity Metrics with SemPy: What the Data Reveals at Scale
SemPy's evaluate_dax bypasses the executeQueries 100k-row cap to pull the full Capacity Metrics model — and reveals the gap no script closes.
Pillar C
Fabric Cost Attribution: Why You Can't Identify Which Pipeline Run Cost You Money
Fabric's OperationID isn't linked to pipeline runs, attribution is item-level only, and the Chargeback app aggregates daily. Here's how to close the gap.
Pillar C
Fabric Capacity Events in the Real-Time Hub: Near-Real-Time Monitoring
Fabric capacity events fire every 30 s and on state change. Route via Eventstream to an Eventhouse + Data Activator for sub-minute throttle alerts.
Pillar C
The Microsoft Fabric Capacity Metrics App: A Complete Guide
Annotated walkthrough of the Fabric Capacity Metrics app: Compute (14-day), Storage (30-day), Throttling, Timepoint, and Health pages — limits and gaps.
Pillar C
The Fabric Chargeback App vs True Cost Attribution: Limits & How to Go Deeper
The Fabric Chargeback app refreshes daily, masks service-principal workloads, and stops at item grain. Here's what it covers and how to go deeper.
Pillar C
Fabric Capacity Alerts That Actually Fire: Real-Time Hub Over Metrics App
Fabric's Capacity Metrics app has no built-in alerts. One Activator rule on Real-Time hub capacity events fires the moment throttling starts.
Pillar C
Fabric Capacity Metrics Retention: 14-Day Compute Limit, 30-Day Storage — and How to Keep History
Fabric Capacity Metrics keeps 14 days of compute detail and 30 days of storage. No setting extends either. Retention matrix and extraction pattern inside.
Pillar C
Fabric Throttling Explained: Why One Query Slows Your Whole Tenant
Fabric throttling is staged across future-capacity time windows, not utilization percentages. One workload's debt blocks every user on the shared capacity.
Pillar C
Real-Time Throttling Triage When the Metrics App Can't Keep Up
The Capacity Metrics app lags 10–15 min — live triage runbook for an active throttle: what to read, in what order, and why pausing is a costly trap.
Pillar C
Predicting Fabric Throttling Before It Happens
Track carry-forward debt slope to forecast Fabric throttle onset before users hit errors — a debt-trajectory method with a worked F32 example.