Final Update: Wednesday, 22 January 2020 10:17 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/22, 09:20 UTC. Our logs show the incident started on 01/22, 08:10 UTC and that during the 1 hour and 10 minutes that it took to resolve the issue all customers in West Europe region may have experienced alerting delays and missed alerts for Log Search Alerts.
We've confirmed that all systems are back to normal with no customer impact as of 01/22, 09:20 UTC. Our logs show the incident started on 01/22, 08:10 UTC and that during the 1 hour and 10 minutes that it took to resolve the issue all customers in West Europe region may have experienced alerting delays and missed alerts for Log Search Alerts.
- Root Cause: The failure was due to an issue with the deployment in one of the backend service.
- Incident Timeline: 1 Hour & 10 minutes - 01/22, 08:10 UTC through 01/22, 09:20 UTC
-Satya
Initial Update: Wednesday, 22 January 2020 09:12 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may have experience facing failure in receiving alerts.
-Satya
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may have experience facing failure in receiving alerts.
- Work Around: None
- Next Update: Before 01/22 13:30 UTC
-Satya
Updated Jan 22, 2020
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