fabric-performance-monitoringlisted

# Microsoft Fabric Performance Monitoring Toolkit for monitoring, diagnosing, and optimizing Microsoft Fabric capacity and workload performance across Spark, Data Warehouse, Lakehouse, and Pipeline workloads. ## When to Use This Skill - Checking Fabric capacity utilization or CU consumption - Diagnosing throttling errors (HTTP 430 / TooManyRequestsForCapacity) - Monitoring Spark VCore usage and concurrency limits - Querying Fabric REST APIs for capacity and workspace health - Generating capacity performance reports - Tuning Spark resource profiles (readHeavy, writeHeavy, balanced) - Investigating job failures in the Monitoring Hub - Analyzing autoscale billing vs capacity-based billing - Reviewing background vs interactive operation patterns - Planning capacity SKU sizing or rightsizing ## Prerequisites - PowerShell 7+ with Az.Fabric module installed - Microsoft Entra ID app registration with Fabric API permissions - Fabric Capacity Admin or Workspace Admin role - Fabric Capacity Metrics app installed (for visual monitoring) ## Core Concepts ### Capacity Units and Spark VCores One Capacity Unit (CU) equals two Apache Spark VCores. Fabric capacity is shared across all workspaces assigned to it, and Spark VCores are shared among notebooks, Spark job definitions, and lakehouses within those workspaces. ### Operation Types Fabric classifies operations as interactive (on-demand, like DAX queries) or background (scheduled, like refreshes and Spark jobs). Background operat