Show an accurate status for database mirroring if it isn't actually running

[Tim_D]

This issue is listed as a known limitation: https://learn.microsoft.com/en-us/fabric/database/mirrored-database/troubleshooting#changes-to-fabri...
The mirrored status should not show as Running if it isn't actually running.  My idea is to add a mechanism to more robustly confirm if the mirroring is actually running or not.  Only show the Running status if it is confirmed to be truly running.  Note that this issue could theoretically occur under other circumstances, so it shouldn't be limited to only the Fabric capacity pausing scenario.

My suggestion would work well in concert with this suggestion if both were implemented: https://community.fabric.microsoft.com/t5/Fabric-Ideas/Alert-on-failures-for-Mirroring-in-fabric/idi...

I also recommend this idea, which would minimize the need for my own idea: https://community.fabric.microsoft.com/t5/Fabric-Ideas/Automatically-resume-DB-mirroring-when-F-capa...

[dbWizard]

Yep, the workarounds I've implemented / tested are one, workspace logging enabled, then an eventstream to grab specific mirroring errors and an activator to fire off on condition to alert you. (super ridiculous capacity hog, I don't recommend it) Build a data factory or pipeline to hit the DMVs of your sql dbs to detect mirroring errors w/ alerts (our current solution because you can't count on the actual mirroring monitor to be accurate)