Final Update: Saturday, 04 July 2020 00:16 UTC
We've confirmed that all systems are back to normal with no customer impact as of 7/4, 01:11 UTC. Our logs show the incident started on 7/4, 00:16 UTC and that during the 55 minutes that it took to resolve the issue 100% of customers in the West Central US region experienced possible alert misfires and/or missing alerts.
-Jack Cantwell
We've confirmed that all systems are back to normal with no customer impact as of 7/4, 01:11 UTC. Our logs show the incident started on 7/4, 00:16 UTC and that during the 55 minutes that it took to resolve the issue 100% of customers in the West Central US region experienced possible alert misfires and/or missing alerts.
- Root Cause: The failure was due to an outage in the back-end compute systems that support Log Search Alerts.
- Incident Timeline: 55 minutes - 7/4, 00:16 UTC through 7/4, 01:11 UTC
-Jack Cantwell
Initial Update: Friday, 03 July 2020 23:45 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience missing or mis-fired alerts.
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience missing or mis-fired alerts.
- Next Update: Before 07/04 01:00 UTC
-Jack Cantwell
Updated Jul 04, 2020
Version 2.0Azure-Monitor-Team
Silver Contributor
Joined February 13, 2019
Azure Monitor Status Archive
Follow this blog board to get notified when there's new activity