← ClaudeAtlas

fabric-rti-perf-remediatelisted

Diagnose and resolve performance issues in Microsoft Fabric Real-Time Intelligence including Eventhouse, KQL databases, Eventstream, and ingestion pipelines. Use when asked to troubleshoot slow KQL queries, high Eventhouse CPU or memory, ingestion latency or failures, Eventstream throughput problems, capacity throttling (HTTP 430), cache policy tuning, materialized view lag, or Always-On configuration. Covers workspace monitoring, Fabric Capacity Metrics app, query optimization, and streaming diagnostics.
PatrickGallucci/fabric-skills · ★ 13 · Data & Documents · score 81
Install: claude install-skill PatrickGallucci/fabric-skills
# Fabric Real-Time Intelligence Performance remediate Systematic toolkit for diagnosing and resolving performance issues across the Microsoft Fabric Real-Time Intelligence stack: Eventhouse, KQL databases, Eventstream, ingestion pipelines, and capacity management. ## When to Use This Skill - Eventhouse queries running slowly or timing out - Ingestion latency or failures into KQL databases - Eventstream throughput bottlenecks or backlog growth - Capacity throttling errors (HTTP 430, TooManyRequestsForCapacity) - High CPU, memory, or cache utilization on Eventhouse - Materialized view lag or freshness issues - Always-On and minimum consumption sizing decisions - Workspace monitoring setup and dashboard interpretation - KQL query optimization for Real-Time Intelligence workloads ## Prerequisites - Microsoft Fabric workspace with Contributor or higher permissions - Workspace monitoring enabled (for query/ingestion logs) - Fabric Capacity Metrics app installed (for capacity-level analysis) - KQL Queryset or Eventhouse query editor access ## Step-by-Step Workflows ### Workflow 1: Diagnose Slow KQL Queries 1. **Enable workspace monitoring** if not already active. See [workspace-monitoring.md](./references/workspace-monitoring.md) 2. **Identify expensive queries** using the diagnostic script: Run [diagnose-slow-queries.kql](./scripts/diagnose-slow-queries.kql) against the monitoring Eventhouse 3. **Analyze query patterns** — filter by Top CPU Time, Top Duration, or Memory