Final Update: Friday, 01 April 2022 22:13 UTC
We've confirmed that all systems are back to normal with no customer impact at the moment. Our logs show the incident started on 4/1, 20:25 UTC and that during the 35m that it took to resolve the issue some of the customers would have experienced data access, query failures and alerting issues. At present all of our services are running as expected.
-Arvind Yadav
We've confirmed that all systems are back to normal with no customer impact at the moment. Our logs show the incident started on 4/1, 20:25 UTC and that during the 35m that it took to resolve the issue some of the customers would have experienced data access, query failures and alerting issues. At present all of our services are running as expected.
- Root Cause: The failure was due to one of the machines going into unhealthy state and unable to serve the requests.
- Incident Timeline: 35 minutes - 4/1, 20:25 UTC through 4/1, 21:00 UTC
-Arvind Yadav
Initial Update: Friday, 01 April 2022 20:48 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience Data access, query failures and delayed or missed Log Search Alerts.
-Arvind Yadav
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience Data access, query failures and delayed or missed Log Search Alerts.
- Work Around: Retry may get successful
- Next Update: Before 04/01 23:00 UTC
-Arvind Yadav
Updated Apr 01, 2022
Version 3.0
Azure-Monitor-Team
Microsoft
Microsoft
