eventstream-cli

Create, update, and inspect Microsoft Fabric Eventstream topologies via REST API and Azure CLI.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill eventstream-cli-paulasilvatech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eventstream-cli
Source: https://github.com/paulasilvatech/Fabric-Agentic-SDLC/tree/main/.github/skills/eventstream-cli
Command: npx skills add https://github.com/paulasilvatech/Fabric-Agentic-SDLC --skill eventstream-cli-paulasilvatech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Building and managing Microsoft Fabric Eventstream real-time ingestion pipelines requires precise REST API calls with base64-encoded topology definitions, LRO polling, and strict payload shapes that are easy to get wrong manually. ## Core Features & Use Cases - Topology Authoring: Create Eventstreams, add sources (Event Hub, IoT Hub, CDC, Custom Endpoint), wire filter and aggregate operators, and connect Lakehouse or Eventhouse destinations through the Fabric definition API. - Read-Only Inspection: List Eventstreams, decode topology graphs, check retention and throughput settings, monitor node health, and retrieve Custom Endpoint Kafka connection metadata. - Lifecycle Control: Pause, resume, and delete Eventstreams with correct request bodies and long-running operation handling. - Use Case: Ask the assistant to create an Eventstream with a SampleData source, add a filter operator keeping events where temperature exceeds 30, and route the filtered output to a DerivedStream — it discovers workspace IDs, builds the topology JSON, base64-encodes it, and polls the deployment to completion. ## Quick Start Ask the assistant to create an Eventstream named SensorIngestion in your dev workspace with a sample data source and a Lakehouse destination.

Frequently Asked Questions about eventstream-cli

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

FAQPage Schema
How do I create a Fabric Eventstream with the REST API?▼

Create an Eventstream by posting to the workspace eventstreams endpoint, then submit a base64-encoded eventstream.json topology via the updateDefinition endpoint. Alternatively, use the Items API to create the item with its inline definition in a single call.

How to add a filter operator to a Fabric Eventstream?▼

Retrieve the current definition with POST getDefinition, decode the base64 topology, append a Filter node whose column and value fields use nested objects with expressionType, then re-encode and submit via updateDefinition. Bare string column references are silently rejected.

How do I get the Kafka connection string for an Eventstream Custom Endpoint?▼

Call GET topology to find the Custom Endpoint source ID, then call GET sources/{sourceId}/connection to retrieve the namespace, event hub name, and access keys. This requires Eventstream.ReadWrite.All scope and explicit user confirmation before exposing credentials.

Why does my Eventstream updateDefinition call return 202 Accepted?▼

The Eventstream definition APIs are long-running operations that return 202 with a Location header. Poll the Location URL until the status reaches Succeeded before treating the topology change as persisted.

Can I query event data through the Eventstream API?▼

No, the Eventstream API only manages topology and configuration, not landed event data. Query events after they land in an Eventhouse or KQL Database using the eventhouse-cli consumption mode instead.

What naming rules apply to Eventstream topology nodes?▼

User-defined sources, operators, DerivedStreams, and destinations must use alphanumeric PascalCase without hyphens, underscores, dots, or spaces. The platform-generated DefaultStream name is the only exception and must not be renamed.