This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Monday, 14 February 2022 11:58 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/14, 10:05 UTC. Our logs show the incident started on 02/14, 08:40 UTC and that during the 1 hour and 25 minutes that it took to resolve the issue, customers with workspace-enabled Application Insights resources in Central Canada may have experienced intermittent log data gaps and incorrect alert activation.
-Surya Garikapati
We've confirmed that all systems are back to normal with no customer impact as of 02/14, 10:05 UTC. Our logs show the incident started on 02/14, 08:40 UTC and that during the 1 hour and 25 minutes that it took to resolve the issue, customers with workspace-enabled Application Insights resources in Central Canada may have experienced intermittent log data gaps and incorrect alert activation.
- Root Cause: The failure was due to back-end dependency.
- Incident Timeline: 1 Hour & 25 minutes - 02/14, 08:40 UTC through 02/14, 10:05 UTC
-Surya Garikapati