Azure fabric documentation for integartion with Service Alerting and monitoring

Question

Good afternoon everyone,

we are implementing Azure Fabric with PowerBI and Azure data factory. I'm looking for dcoumentation on how to set up my service management to monitor and alert for my ETL JObs, workspce capacities, Mirroring of data into Fabric etc. so I can automate the alterting and raising of incidents etc. Can you point me in the direction of docuemntation so I can see what I get out of the box but also what is available via the Rest API's in Azure Fabric if I have work space monitoring enabled etc. We use ServiceNow.

Thanks

Answer 1

Hi @Stuart Connor

Microsoft Fabric has built-in features to monitor pipelines, capacities, and other workloads.

For pipeline monitoring and alerts, you can use the Monitoring Hub and configure pipeline failure notifications: https://learn.microsoft.com/fabric/admin/monitoring-hub

https://learn.microsoft.com/fabric/data-factory/create-alerts-for-pipeline-runs

If you need more detailed monitoring, Workspace Monitoring collects logs and metrics in a read-only Eventhouse that you can query by using KQL: https://learn.microsoft.com/fabric/fundamentals/workspace-monitoring-overview

To monitor capacity usage and throttling, you can use the Capacity Metrics App: https://learn.microsoft.com/fabric/enterprise/metrics-app

For automation, Microsoft Fabric also provides REST APIs that you can use to retrieve job information and build your own monitoring solution:

https://learn.microsoft.com/rest/api/fabric/

If you're using ServiceNow, there isn't a built-in integration with Fabric. A common approach is to use Power Automate or Azure Logic Apps to send alerts and create incidents in ServiceNow.

I hope these documents help. If you're looking for guidance on a specific area, such as mirroring or capacity monitoring, let us know.

Answer 2

I think the main point is that Fabric keeps all detailed pipeline, mirroring, and capacity logs in Workspace‑Monitoring’s Eventhouse, and the built‑in KQL views are the documented way to read them. Alerts are made in Logic Apps or Azure Monitor by running saved KQL, and incidents go to ServiceNow through its connector or REST API.

Answer 3

Use three monitoring layers. Start with Fabric Monitoring hub for run status and history. Enable Workspace monitoring in each workspace; it creates a monitoring Eventhouse and read-only KQL database. Query ItemJobEventLogs and FabricDataPipelinesActivityRunsLogs for failures and duration, and mirrored-database operation tables for replication status and latency.

For proactive alerts, use scheduled-run failure notifications for email, or Fabric job events with Activator for rule-based notifications. For ServiceNow, route alerts through an Azure Logic App or webhook that creates incidents containing the workspace, item, run ID, status, and error context. Use the Fabric Capacity Metrics app for CU utilization, throttling, and item-level consumption.

For automation, the Fabric Job Scheduler REST API lists job instances per item, while Mirroring exposes status APIs. If Azure Data Factory remains outside Fabric, send diagnostic logs to Log Analytics and trigger Azure Monitor alerts with action groups. Test permissions, retention, and duplicate suppression before production.