Final Update: Thursday, 24 October 2019 10:22 UTC
We've confirmed that all systems are back to normal with no customer impact as of 10/24, 10:26 UTC. Our logs show the incident started on 10/24, 06:26 UTC and that during the 4 hours that it took to resolve the issue ~10% of customers from West Europe region may have experienced failures while performing log search operations and possible missed alerts for resources hosted in this region.
-Mohini
We've confirmed that all systems are back to normal with no customer impact as of 10/24, 10:26 UTC. Our logs show the incident started on 10/24, 06:26 UTC and that during the 4 hours that it took to resolve the issue ~10% of customers from West Europe region may have experienced failures while performing log search operations and possible missed alerts for resources hosted in this region.
- Root Cause: The failure was due to issue with one of our dependent service.
- Incident Timeline: 4 Hours - 10/24, 06:26 UTC through 10/24, 10:26 UTC
-Mohini
Initial Update: Thursday, 24 October 2019 07:40 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience alerting failure in West Europe region.
-Rama
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience alerting failure in West Europe region.
- Work Around: None
- Next Update: Before 10/24 11:00 UTC
-Rama
Updated Oct 24, 2019
Version 2.0Azure-Monitor-Team
Former Employee
Joined February 13, 2019
Azure Monitor Status Archive
Follow this blog board to get notified when there's new activity