Final Update: Friday, 01 January 2021 15:42 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/01, 15:30 UTC. Our logs show the incident started on 01/01, 08:20 UTC and that during the 7 Hours 10 Minutes that it took to resolve the issue some of customers may have experienced issues with delayed or wrongly fired Log Search alerts or experienced difficulties accessing data for resources hosted in China East Region.
-
Root Cause: We identified the issue was caused by a configuration setting.
- Incident Timeline: 7 Hours & 10 minutes - 01/01, 08:20 UTC through 01/01, 15:30 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.
-Madhav
Update: Friday, 01 January 2021 13:27 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience issues with missed, delayed or wrongly fired Log Search Alerts or experience difficulties accessing data for resources hosted in China East 2 region.
- Root Cause: The failure was due to a recent deployment in one of the backend services.
- Next Update: Before 01/01 15:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Madhav
Initial Update: Friday, 01 January 2021 10:08 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience issues with missed, delayed or wrongly fired Log Search Alerts or experience difficulties accessing data for resources hosted in China East 2 region.
- Work Around: None
- Next Update: Before 01/01 13:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anmol
