Summary
Without monitoring, failures in data pipelines, dataflows, and notebooks go undetected — leading to stale reports, missed SLAs, and reactive troubleshooting. In this module, you learned how Microsoft Fabric provides tools to give you visibility into what's happening across your workspace and to automate responses when problems occur.
You explored how the monitoring hub serves as a centralized dashboard for tracking activity status, investigating failures, viewing historical run data, and configuring failure notifications. You also learned how workspace monitoring extends this capability by collecting diagnostic logs in an Eventhouse database for deeper, query-based analysis. Finally, you learned how Activator responds to Fabric job events — such as pipeline failures and notebook errors — by triggering actions like sending alerts, posting Teams messages, or running a Fabric activity to remediate the issue automatically, rather than waiting for someone to check the monitoring hub.
With these tools, you can build a monitoring strategy that catches failures early and ensures the right people are notified when something goes wrong.
To learn more, see Use the monitoring hub, What is workspace monitoring?, and What is Activator?.