Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article outlines various methods for monitoring your mirrored database after it's set up, including using the Fabric portal, programmatic monitoring, and leveraging workspace monitoring.
Monitor from the Fabric portal
Once the mirrored database is configured, you can monitor the current state of replication. The Monitor replication section shows you the database level status, and a list of tables under replication along with the corresponding status, total rows replicated, and the last completed time to refresh mirrored table from source.
Tip
If you observe a delay in the appearance of mirrored data, follow the troubleshooting guide to debug the potential issue.
The following are the possible statuses for the replication:
| Monitor | Status |
|---|---|
| Database level | Running: Replication is currently running bringing snapshot and change data into OneLake. Running with warning: Replication is running, with transient errors. Stopping/Stopped: Replication has stopped. Error: Fatal error in replication that can't be recovered. |
| Table level | Running: Data is replicating. Running with warning: Warning of nonfatal error with replication of the data from the table. Stopping/Stopped: Replication has stopped. Error: Fatal error in replication for that table. |
Monitor programmatically
You can monitor the mirrored databases programmatically by using the REST APIs or SDK. Learn more from Microsoft Fabric mirroring public REST API on how to get mirroring status for the mirrored database or specific tables.
Use workspace monitoring
Workspace monitoring is an observability feature in Microsoft Fabric that enables developers and admins to access detailed logs and performance metrics of their workspaces.
Mirroring in Fabric supports operation logs in workspace monitoring to provide a more comprehensive monitoring experience for your mirrored databases. You can use these logs to monitor execution and performance of your mirrored database, including data replication, table changes, mirroring status, failures, and replication latency.
To get started, enable monitoring in your workspace. Once the monitoring of your workspace is enabled, the mirrored database execution logs are automatically ingested into the MirroredDatabaseTableExecution table in the monitoring KQL database. Learn more about the available logs and the structure from Mirrored database operation logs.
Then you have full access to an advanced monitoring experience for mirrored database:
Derive insights on-demand: Query the granular operation logs directly using KQL in the monitoring database to get instant access to the information you need.
Build customized monitoring dashboards: With the monitoring database, you can integrate data into your preferred tools like Power BI and Real-Time Dashboards to create dashboards tailored to your needs.
Set up alerting: Set up alerts based on the logs and metrics you’re tracking.
