Momentum One Academy · glossary
Monitoring Hub
Definition
In Microsoft Fabric, the Monitoring Hub—called the Monitor hub in current Microsoft documentation—is a central operations surface for observing job execution, alerts, capacity and cost, applications, and agents. It lets users spot activity and investigate problems across Fabric from one place. The hub is currently in preview and shows only activities for items the signed-in user may view. 1
Where it sits in Fabric
The hub sits above individual workloads as a cross-workload monitoring and administration experience. In Data Factory, the new Monitoring hub preview can show pipeline health across workspaces, run history, execution relationships, run details, alerts, and rerun controls. It complements workload-specific observability: workspace monitoring can persist pipeline and activity logs in an eventhouse for KQL queries and custom reports, while the Capacity Metrics app supports deeper capacity-usage analysis. 2 3
When to use it
Use the hub as an operator’s first check: confirm a scheduled job completed, find an unhealthy pipeline, inspect a failed run, follow upstream or downstream execution, or see whether capacity health and throttling may explain a delay. Use other detail surfaces for durable, queryable history, organization-wide capacity analysis, or governance evidence. Capacity actions require suitable administrator permissions, and the capacity view is also preview. 4
Practical example
A morning Data Pipeline copies orders into a Lakehouse and starts a transformation. If the load fails, an operator filters the Monitoring Hub to the pipeline, opens the run ID, reviews activity errors and duration, follows upstream or downstream runs, and checks capacity status and throttling. After correcting the source issue, the operator can rerun the full pipeline or selected failed activities in the new preview experience. 3 4
Production caution
Treat the hub as an operational console, not the only audit store or a guarantee of safe recovery. Preview behavior can change, visibility is permission-scoped, and a rerun can repeat writes or trigger downstream side effects unless the pipeline is idempotent. Retain the logs and controls needed for incident review in the relevant monitoring and governance systems, and test rerun behavior before relying on it in production.
Workshop connection
In Module 3, use Monitoring Hub to operate the Data Pipeline built for ingestion and transformation. In Module 9, correlate job symptoms with Fabric Capacity utilization, CU consumption, and throttling instead of tuning a pipeline in isolation. In Module 10, place the hub inside Governance: permissions determine what operators can see, while broader governance, audit, and compliance practices need their own controls and evidence. Microsoft separates monitoring Fabric operations from measuring governance health, so the hub is an operational input, not the complete governance program. 5
Continue building reliable Fabric operations with Momentum One Academy’s Fabric Production Workshop.
References
Plan your workshop