eventstream-cli

Create, configure, and inspect Microsoft Fabric Eventstream topologies via REST APIs.

1.1k|301|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/microsoft/skills-for-fabric --skill eventstream-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eventstream-cli
Source: https://github.com/microsoft/skills-for-fabric/tree/main/plugins/fabric-skills/skills/eventstream-cli
Command: npx skills add https://github.com/microsoft/skills-for-fabric --skill eventstream-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Managing Fabric Eventstream real-time ingestion pipelines requires navigating complex REST APIs, base64-encoded definitions, LRO polling, and strict topology rules, which is error-prone when done manually.

Core Features & Use Cases

  • Authoring mode: Create Eventstreams, deploy full topologies with sources, operators, and destinations, update definitions, pause/resume, and delete items via the Fabric REST API.
  • Consumption mode: List and inspect Eventstreams, decode topology graphs, check retention and throughput settings, validate configurations, and retrieve Custom Endpoint connection metadata.
  • Use Case: Ask the assistant to create an Eventstream with a SampleData source, add a Filter operator for high-temperature events, and wire the output to a Lakehouse destination, with all API calls, base64 encoding, and LRO polling handled correctly.

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 the item with POST /v1/workspaces/{id}/eventstreams, then build the topology JSON and submit it base64-encoded via POST .../updateDefinition. Alternatively, use POST /items with an inline definition to create the Eventstream and topology in one call.

How do I add a filter operator to an Eventstream?

Retrieve the current definition with POST .../getDefinition, decode the base64 eventstream.json, add a Filter node whose column and value 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 .../eventstreams/{id}/topology to find the Custom Endpoint source ID, then GET .../sources/{sourceId}/connection. This returns the namespace, event hub name, and access keys, and requires the Eventstream.ReadWrite.All scope plus explicit user confirmation.

Why does my Eventstream updateDefinition call return 202 Accepted?

The definition APIs are long-running operations that return 202 with a Location header. Poll the Location URL until the status is Succeeded before treating the update as complete.

What are the naming limits for Eventstream topology nodes?

User-defined node names must be alphanumeric PascalCase with no hyphens, underscores, dots, or spaces. The platform-generated DefaultStream name is the exception, and a topology may contain at most 11 CustomEndpoint and direct-ingestion nodes.

Can I query event data through the Eventstream API?

No. The Eventstream API manages topology and configuration only. To query landed event data, use the eventhouse-cli consumption mode against the Eventhouse or KQL Database where the events are stored.