Final Update: Wednesday, 06 July 2022 12:54 UTC
We've confirmed that all systems are back to normal with no customer impact as of 07/06, 11:25 UTC. Our logs show the incident started on 07/06, 05:45 UTC and that during the 5 hours & 40 minutes that it took to resolve the issue, some of the customers using Azure Monitor who may have experienced issues with missed alerts or missed alerts notifications in Korea Central region.
-Sai Kumar
We've confirmed that all systems are back to normal with no customer impact as of 07/06, 11:25 UTC. Our logs show the incident started on 07/06, 05:45 UTC and that during the 5 hours & 40 minutes that it took to resolve the issue, some of the customers using Azure Monitor who may have experienced issues with missed alerts or missed alerts notifications in Korea Central region.
- Root Cause: The failure was due to a backend dependency service becoming unhealthy.
- Incident Timeline: 5 Hours & 40 minutes - 07/06, 05:45 UTC through 07/06, 11:25 UTC
-Sai Kumar
Initial Update: Wednesday, 06 July 2022 10:25 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customer using Azure Monitor who may experience issues with missed alerts or missed alerts notifications.
-Sai Kumar
We are aware of issues within Log Search Alerts and are actively investigating. Some customer using Azure Monitor who may experience issues with missed alerts or missed alerts notifications.
- Work Around: NA
- Next Update: Before 07/06 14:30 UTC
-Sai Kumar
Updated Jul 06, 2022
Version 2.0
Azure-Monitor-Team
Microsoft
Microsoft
