ChiefOSby ConversintStart free
Menu
← Back to the library
Data science and analytics

Fabric eventhouse workflow

Fabric eventhouse workflow. 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. Authors and queries Fabric Eventhouse and KQL databases: tables, functions, policies, materialized views, ingestion, and read-only KQL for real-time and time-series analytics. All KQL database work belongs here, table creation and simple queries included. An Eventstream item is eventstream-cli; an Event.

Works with the context you provideVersion 1.0.0

Fabric eventhouse workflow

Use this skill for the outcome in its description. Start with the supplied request and evidence, identify the specific task, and distinguish planning from execution. Do not trigger solely because the subject happens to be fashion, retail, or a technology named in an example. Read `references/execution-contract.md` before applying a retained source method.

Select the narrowest matching method below, then read its full entrypoint and the resources it requires. If multiple methods cover the same outcome, choose the one matching the user's environment and inputs; do not run them all. Retain each method's input requirements, decision steps, validation, output structure, and failure handling. If prerequisites are absent, use its honest proposal-only fallback or state that its documented path is blocked.

  • **PatrickGallucci/fabric-rti-perf-remediate**: 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. Read `references/PatrickGallucci/skills/fabric-rti-perf-remediate/SKILL.md`.
  • **microsoft/eventhouse-cli**: Authors and queries Fabric Eventhouse and KQL databases: tables, functions, policies, materialized views, ingestion, and read-only KQL for real-time and time-series analytics. All KQL database work belongs here, table creation and simple queries included. An Eventstream item is eventstream-cli; an Event Schema Set is eventschemaset-cli. Read `references/microsoft/skills/eventhouse-cli/SKILL.md`.

Return the requested deliverable with evidence, assumptions, validation performed, unresolved dependencies, and actual execution status. Source-specific results must be verified independently; importing these methods does not establish a working service connection.