This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Friday, 08 April 2022 00:54 UTC
-Yukti Sharma
We've confirmed that all systems are back to normal with no customer impact as of 04/07, 21:10 UTC. Our logs show the incident started on 04/06, 21:10 UTC and that during the 24 hours that it took to resolve the issue, customers may have seen data gaps for data type custom Logs and would have experienced failures in data reports, query and alerting configured.
- Root Cause: The failure was due to backend services going in unhealthy state.
- Incident Timeline: 24 Hours - 04/06, 21:10 UTC through 04/07, 21:10 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
-Yukti Sharma