fabric-data-agent-perf-remediate — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited fabric-data-agent-perf-remediate (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Systematic toolkit for diagnosing and resolving performance issues in Microsoft Fabric Data Agents, Operations Agents, and their underlying Spark compute and data source infrastructure.
https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/itemsAgent performance issue reported
├── Slow response times?
│ ├── First query after idle? → Spark session startup (see Workflow 1)
│ ├── All queries slow? → Resource profile mismatch (see Workflow 2)
│ └── Intermittent slowness? → Capacity throttling (see Workflow 3)
├── Incorrect query results?
│ ├── Wrong tables/columns? → Data source instructions (see Workflow 4)
│ ├── SQL syntax errors? → Example query validation (see Workflow 5)
│ └── Stale data? → Lakehouse table maintenance (see Workflow 6)
├── Agent not responding?
│ ├── HTTP 430 errors? → Concurrency limits (see Workflow 3)
│ ├── Connection failures? → Data source config (see Workflow 4)
│ └── Operations Agent stuck? → Playbook/action config (see Workflow 7)
└── Cost concerns?
├── Unexpected charges? → Autoscale Billing audit (see Workflow 8)
└── Over-provisioned? → SKU right-sizing (see Workflow 8)Symptoms: First query takes 2-5 minutes, subsequent queries are fast.
| Scenario | Expected Startup |
|---|---|
| Default, no custom libraries | 5-10 seconds |
| Default + library dependencies | 35 seconds - 5 minutes |
| High regional traffic | 2-5 minutes |
| Private Links / Managed VNet | 2-5 minutes |
| Network security + libraries | 2.5-10 minutes |
Resolution steps: See workflow-spark-startup.md
Symptoms: Consistently slow reads or writes across all agent queries.
| Profile | Use Case | VOrder | OptimizeWrite |
|---|---|---|---|
writeHeavy | High-frequency ingestion (default) | Disabled | Disabled |
readHeavyForPBI | Power BI dashboard queries | Enabled | Enabled (1GB bin) |
readHeavyForSpark | Interactive Spark analytics | Disabled | Enabled (128MB bin) |
custom | User-defined workload tuning | Configurable | Configurable |
Resolution steps: See workflow-resource-profiles.md
Symptoms: TooManyRequestsForCapacity errors, jobs queued or rejected.
| SKU | Spark VCores | Queue Limit |
|---|---|---|
| F2 | 4 | 4 |
| F8 | 16 | 8 |
| F64 | 128 | 64 |
| F128 | 256 | 128 |
| F256 | 512 | 256 |
Formula: 1 Capacity Unit = 2 Spark VCores
Resolution steps: See workflow-capacity-throttling.md
Symptoms: Agent queries wrong tables, returns irrelevant results, or fails to connect.
Data Agents use three configuration layers that all affect query quality:
Resolution steps: See workflow-data-source-config.md
Symptoms: Agent ignores example queries, generates incorrect SQL/KQL syntax.
Key rule: The Fabric Data Agent only uses queries that contain valid SQL/KQL syntax AND match the schema of the selected tables. Queries that fail validation are silently ignored.
Resolution steps: See workflow-example-queries.md
Symptoms: Queries over Delta tables are slow, small file problem, stale statistics.
Three maintenance operations available via REST API:
| Operation | Purpose |
|---|---|
| Bin-compaction | Consolidate small files into optimal sizes |
| V-Order | Optimize Parquet layout for read performance |
| Vacuum | Remove unreferenced files older than retention |
Resolution steps: See workflow-table-maintenance.md
Symptoms: Operations Agent not triggering actions, playbook failures.
Operations Agent definition requires: goals, instructions, at least one KustoDatabase data source, at least one PowerAutomateAction, and shouldRun: true.
Resolution steps: See workflow-operations-agent.md
Symptoms: Unexpected costs, capacity contention between Spark and other workloads.
Resolution steps: See workflow-autoscale-billing.md
| Script | Purpose |
|---|---|
| Get-FabricAgentDiagnostics.ps1 | Collect agent config, capacity state, and Spark metrics |
| Test-ExampleQueries.ps1 | Validate example queries against data source schema |
| Invoke-TableMaintenance.ps1 | Run bin-compaction, V-Order, and vacuum on Lakehouse tables |
| Error | Likely Cause | First Action |
|---|---|---|
| HTTP 430 | Capacity VCore limit | Check Monitoring Hub for active jobs |
| Query timeout | Resource profile mismatch | Switch to readHeavyForSpark |
| Wrong columns | Missing data source instructions | Update schema descriptions |
| Ignored examples | Invalid SQL/KQL syntax | Validate with Test-ExampleQueries.ps1 |
| 2-5 min startup | Private Links or high traffic | Check workspace networking config |
| Stale results | Missing table maintenance | Run bin-compaction + V-Order |
| Agent not running | shouldRun: false | Check Operations Agent definition |
| Autotune disabled | Runtime > 1.2 or HC mode | Verify Fabric Runtime version |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.