fabric-rti-perf-remediate
Skill17 starsChanged 9 months agoMITView on GitHub
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.
In this repository24 other files it gives its agents.
- fabric-data-agent-perf-remediateSkill
- fabric-data-agent-remediateSkill
- fabric-data-agentSkill
- fabric-data-factory-perf-remediateSkill
- fabric-dataflows-perf-remediationSkill
- fabric-delta-spark-perfSkill
- fabric-iqSkill
- fabric-lakehouse-access-controlSkill
- fabric-lakehouse-perf-remediateSkill
- fabric-lakehouse-views-perf-remediateSkill
- fabric-network-remediateSkill
- fabric-notebook-perf-remediateSkill
- fabric-onelake-perf-remediateSkill
- fabric-pandas-perf-remediateSkill
- fabric-pbi-perf-remediateSkill
- fabric-pbi-security-remediateSkill
- fabric-performance-monitoringSkill
- fabric-pyspark-perf-remediateSkill
- fabric-rest-api-perf-remediateSkill
- fabric-rest-api-remediateSkill
- fabric-spark-compute-perf-remediateSkill
- fabric-spark-compute-remediateSkill
- fabric-spark-perf-remediateSkill
- fabric-udf-perf-remediateSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Always-On and minimum consumption sizing decisions
- Distinctive: line 33
Enable workspace monitoring: if not already active. See workspace-monitoring.md
- Distinctive: line 35
Run diagnose-slow-queries.kql against the monitoring Eventhouse
- Distinctive: line 53
Evaluate sizing options: Always-On minimum consumption, cache policy adjustments, or SKU upgrade
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Enable workspace monitoring if not already active. See workspace-monitoring.md
- Identify expensive queries using the diagnostic script: Run diagnose-slow-queries.kql against the monitoring Eventhouse
- Analyze query patterns — filter by Top CPU Time, Top Duration, or Memory Peak
- Apply KQL optimization rules from kql-optimization.md
- Validate improvement by re-running the query and comparing duration/CPU metrics
Workflow 2: Troubleshoot Ingestion Issues
- Check ingestion results logs using diagnose-ingestion.kql
- Review Eventstream data insights — check IncomingMessages, OutgoingMessages, BackloggedInputEvents, and WatermarkDelay metrics
- Identify failure patterns — deserialization errors, schema mismatches, throttling
- Apply throughput tuning per ingestion-remediate.md
- Validate pipeline health by monitoring runtime logs on source and destination nodes
Workflow 3: Resolve Capacity Throttling
- Open the Fabric Capacity Metrics app — filter to your capacity and workspace
- Check Eventhouse UpTime CU consumption — identify if a single Eventhouse dominates
- Run capacity diagnostics using diagnose-capacity.kql
- Evaluate sizing options: Always-On minimum consumption, cache policy adjustments, or SKU upgrade
- Apply recommendations from capacity-and-sizing.md
remediate Quick Reference
| Symptom | First Check | Script |
| Slow queries | Workspace Monitoring → EH Queries tab | diagnose-slow-queries.kql |
| Query throttling (HTTP 430) | Capacity Metrics app → CU utilization | diagnose-capacity.kql |
| Ingestion failures | Eventstream → Runtime logs tab | diagnose-ingestion.kql |
| High ingestion latency | Eventstream → Data insights → WatermarkDelay | diagnose-ingestion.kql |
| Materialized view stale | .show materialized-views command | diagnose-slow-queries.kql |
| Cold storage scans | Cache policy vs query time range | diagnose-capacity.kql |
| Eventhouse wake-up latency | Always-On setting disabled | capacity-and-sizing.md |
| Eventstream backlog growing | Throughput setting mismatch | ingestion-remediate.md |
References
- KQL Query Optimization Guide — Best practices for writing performant KQL
- Ingestion remediate Guide — Eventstream, batching, and streaming diagnostics
- Capacity and Sizing Guide — Always-On, cache policies, CU consumption
- Workspace Monitoring Setup — Enabling and using monitoring tables and dashboards
- KQL Best Practices (Microsoft)
- Eventhouse Compute Observability
- Eventstream Monitoring
- Fabric Capacity Metrics App
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

