Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.
3.1.1. Monitor Hub: The Central Observatory
💡 First Principle: Monitor Hub provides a unified view of all Fabric activities across workspaces. It's the first place to look when investigating issues.
Scenario: A daily sales report shows stale data. The data engineer needs to determine whether the pipeline failed, the notebook errored, or the semantic model refresh failed. Monitor Hub shows all activities in one place.
Monitor Hub Capabilities
| Feature | Purpose | Use Case |
|---|---|---|
| Activity filtering | Filter by status, type, time | Find failed runs |
| Historical runs | View past executions | Trend analysis |
| Drill-down | Examine activity details | Root cause analysis |
| Cross-workspace | See activities across workspaces | Enterprise monitoring |
Filtering Activities
- By Status: Succeeded, Failed, In Progress, Cancelled
- By Type: Pipeline, Dataflow, Notebook, Refresh
- By Time: Custom date range
- By Submitted By: User who triggered the activity
⚠️ Common Pitfall: Looking at logs without filtering by status. Filter by "Failed" first to quickly identify problems, then expand investigation.