eventstream-cli

1> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry
2> `x-ms-fabric-skill: eventstream-cli` (`az rest`: `--headers "x-ms-fabric-skill=eventstream-cli"`),
3> including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.
4 
5> **CRITICAL NOTES**
6> 1. To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
7> 2. To find the item details (including its ID) from workspace ID, item type, and item name: list all items of that type in that workspace and, then, use JMESPath filtering
8> 3. **Skill disambiguation**: use `eventstream-cli` for the Eventstream item itself -- how events flow from source through operators to destinations. Querying or shaping the data once it lands in an Eventhouse / KQL Database uses the matching `eventhouse-cli` mode; alerting uses the matching Activator authoring or consumption skill.
9 
10# Fabric Eventstream -- CLI Skill
11 
12This one skill owns Fabric Eventstream real-time ingestion topologies: sources, operators, destinations, routing, retention and health.
13 
14It is a **mode dispatcher** and contains NO procedures. Pick the mode that matches the request from the table below, then **read the matching `references/<mode>.md` file end to end with your file-reading tool BEFORE issuing a single command**. That file holds the endpoints, payload shapes, templates and gotchas; acting without it produces wrong payloads and wrong results.
15 
16## Mode selection
17…