eventstream-consumption-cli

Inspect and monitor Fabric Eventstream topologies via the Items REST API.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/9vantage/skills-for-fabric-clone --skill eventstream-consumption-cli-9vantage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eventstream-consumption-cli
Source: https://github.com/9vantage/skills-for-fabric-clone/tree/main/plugins/fabric-skills/skills/eventstream-consumption-cli
Command: npx skills add https://github.com/9vantage/skills-for-fabric-clone --skill eventstream-consumption-cli-9vantage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fabric Eventstreams are opaque real-time ingestion pipelines whose graph structure is stored as base64-encoded definitions, making it hard to discover, inspect, and validate them without opening the Fabric portal. This Skill provides CLI-driven workflows to list Eventstreams, decode their topology, validate configurations, and retrieve connection credentials. ## Core Features & Use Cases - Discovery and Listing: List all Eventstreams in a workspace and resolve workspace/item names to IDs using JMESPath filtering over the Fabric Items REST API. - Topology Inspection: Decode the base64 eventstream.json definition or use the Topology API to trace event flow from sources through operators to destinations. - Configuration Validation: Check source/destination wiring, connection IDs, retention policies (1-90 days), and throughput levels against known constraints. - Credential Retrieval: Fetch Kafka/Event Hub connection strings for Custom Endpoint sources via the Topology API connection endpoint. - Use Case: An engineer needs to verify that an Eventstream routes IoT Hub events into an Eventhouse with correct retention settings; this Skill walks through listing the item, decoding its graph, and validating each node. ## Quick Start Ask the assistant to list all Eventstreams in your Fabric workspace and inspect the topology of a specific one by name.

Frequently Asked Questions about eventstream-consumption-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list all Eventstreams in a Fabric workspace?

Call GET https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/eventstreams via az rest with the Fabric resource audience. Use JMESPath filtering such as value[?displayName=='name'] to find a specific Eventstream by name.

How to inspect an Eventstream topology from the command line?

Use POST .../eventstreams/{id}/getDefinition, extract the eventstream.json part payload, and base64-decode it to see sources, operators, streams, and destinations. For runtime status without decoding, call GET .../topology instead.

How do I get the Kafka connection string for a Fabric Eventstream custom endpoint?

Call GET .../eventstreams/{id}/topology to find the Custom Endpoint source ID, then GET .../sources/{sourceId}/connection. This endpoint requires Eventstream.ReadWrite.All permission and returns access keys and connection strings.

What is the difference between Eventstream and Eventhouse in Microsoft Fabric?

Eventstream is a real-time event ingestion and routing pipeline, while Eventhouse is a KQL-based analytics database. Eventstreams route events into destinations like Eventhouse; use eventhouse-consumption-cli for KQL queries on landed data.

Why does the Eventstream definition API return empty properties for custom endpoints?

The POST getDefinition endpoint intentionally returns empty properties for Custom Endpoint sources. Retrieve Kafka and Event Hub connection details through the Topology API's /sources/{sourceId}/connection endpoint instead.

Can I modify an Eventstream topology with this consumption skill?

No, this skill is read-only for listing, inspecting, and validating Eventstreams. Use the eventstream-authoring-cli skill for creating or modifying Eventstream topology and configuration.