Author: Anasheh Boisvert - Senior Program Manager
_________________________________________________________
Do you ever wonder how much data volume is flowing in and out of your Eventstream? Or wish you could query the health or errors in one place without selecting each Eventstream component? Now you can.
Eventstream observability through Workspace Monitoring provides monitoring to your streaming pipelines with a single toggle and minimal configuration. Simply enable Workspace Monitoring in your workspace settings, and three purpose-built tables are automatically created in your monitoring Eventhouse — no code, minimal setup, and no managing infrastructure.
In a few steps, you can start collecting health, performance, and error data from every Eventstream in your workspace — all queryable with KQL in a monitoring Eventhouse that Fabric creates and manages for you.
Figure: High-level overview image showing the monitoring Eventhouse with the three Eventstream tables.
Why this matters
Eventstreams are often at the heart of real-time data pipelines. They connect sources to destinations, apply transformations, and keep data flowing. But streaming pipelines are only as reliable as your ability to see what’s happening inside them.
Capabilities with Eventstream workspace monitoring:
- See every node’s status — running, paused, failed, or creating — across all Eventstreams in a workspace.
- Track data volumes over time — incoming messages, outgoing messages, bytes in, bytes out — with per-minute granularity.
- Spot processing bottlenecks before they become outages — watermark delay and backlogged event counts tell you when processing is falling behind.
- Identify error patterns — runtime errors, deserialization failures, and data conversion issues, all broken down by type and time window.
- Build custom KQL queries, dashboards, and alerts on top of the monitoring data — using the same Eventhouse and KQL experience you already know.
What’s included in Preview
When you enable workspace monitoring, Fabric automatically creates three Eventstream tables in your monitoring Eventhouse database:
EventStreamNodeStatus
Tracks the health of every node in your Eventstream — sources, destinations, default streams, and derived streams. Each row tells you: is this node running? When was it last checked? What type of node is it?
Node status is updated approximately every six hours, giving you a historical record of node health over time.
EventStreamMetrics
Captures data flow metrics updated every minute. This is where you go to answer the big questions: How much data is flowing? Is processing keeping up? Where’s the bottleneck?
Key metrics include:
- Incoming/Outgoing Messages and Bytes — Volume flowing through your streams.
- Watermark Delay — How far behind processing is from the latest event. A rising delay is an early warning sign.
- Backlogged Input Events — Events waiting to be processed. High backlogs mean your processing capacity needs attention.
- Input and Output Events — Event counts at the processor level, so you can verify data is making it all the way through.
EventStreamErrorMetrics
Tracks error counts by type, updated every minute. Instead of guessing what went wrong, you can see exactly how many runtime errors, deserialization errors, and data conversion errors occurred — and when.
For example, a spike in deserialization errors usually means the data format being sent doesn’t match what your Eventstream expects — a common issue when upstream systems change their schema without notice.
Get started in minutes
Setting up monitoring takes less than a minute:
1. Open your workspace and go to Workspace settings.
2. Select Monitoring in the left navigation.
3. Select + Eventhouse — Fabric creates the monitoring database automatically.
4. Open the monitoring Eventhouse and start querying your Eventstream tables.
That’s it. No configuration, no SDK, no code.
Workspace_settings_panel_with_the_Monitoring_section_selected_in_the_left_naviga
Figure: The Workspace settings > Monitoring panel showing the + Eventhouse button.
Additional step for existing Eventstreams
If you enable monitoring in a workspace that already has Eventstreams, those existing Eventstreams need to be republished once for monitoring data to start flowing. This is because the monitoring configuration is applied at publish time.
Open the existing Eventstream, make a small edit (add and remove a node, for example), and select Publish. New Eventstreams created after you enable monitoring will work automatically — no extra steps needed.
What’s next
This is the start. This preview includes metrics, error counts, and node status—providing a foundation for understanding your Eventstreams. Future releases will add:
- Diagnostic logs — detailed error messages with root cause and suggested actions, so you can troubleshoot without opening a support ticket.
- More frequent node status updates — to close the gap between current 6-hour emissions and real-time awareness.
- Additional metrics — based on your feedback and real-world usage patterns.
Try it today
1. Enable workspace monitoring in your workspace settings.
2. Open the monitoring Eventhouse and explore the Eventstream tables.
3. Run a few queries and see what your data is telling you.
We’d love to hear what you think. Share your feedback through the Fabric community, Fabric Ideas, or directly with our team (nrtpmteam@microsoft.com). Your input shapes what we build n...
Learn more