Final Update: Tuesday, 31 March 2020 16:59 UTC
We've confirmed that all systems are back to normal with no customer impact as of 03/31,16:50 UTC. Our logs show the incident started on 03/31, 11:30 UTC and that during the 5 hours and 20 minutes that it took to resolve the issue some customers using Log Analytics in West Europe experienced issues with data access and ingestion latency which may have caused Log Search Alerts to be missed, delayed or incorrect for resources in the region.
-Jayadev
We've confirmed that all systems are back to normal with no customer impact as of 03/31,16:50 UTC. Our logs show the incident started on 03/31, 11:30 UTC and that during the 5 hours and 20 minutes that it took to resolve the issue some customers using Log Analytics in West Europe experienced issues with data access and ingestion latency which may have caused Log Search Alerts to be missed, delayed or incorrect for resources in the region.
- Root Cause: The failure was due to issues with one of the backend services.
- Incident Timeline: 5 Hours & 20 minutes - 03/31, 11:30 UTC through 03/31,16:50 UTC
-Jayadev
Initial Update: Tuesday, 31 March 2020 13:42 UTC
We are aware of issues within Log Analytics and are actively investigating. Our logs show the incident started on 03/31 ,11:30 UTC and some customers may experience data access or intermittently experience data ingestion Latency issues in West Europe.
-Syed
We are aware of issues within Log Analytics and are actively investigating. Our logs show the incident started on 03/31 ,11:30 UTC and some customers may experience data access or intermittently experience data ingestion Latency issues in West Europe.
- Work Around: None
- Next Update: Before 03/31 16:00 UTC
-Syed
Updated Mar 31, 2020
Version 3.0
Azure-Monitor-Team
Microsoft
Microsoft
