This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Sunday, 05 April 2020 18:31 UTC
We've confirmed that all systems are back to normal with no customer impact as of 04/05, 17:30 UTC. Our logs show the incident started on 04/05, 16:30 UTC and that during the 1 hour that it took to resolve the issue some customers using Log Search Alerts in multiple regions with running queries on tables that have no data and may have experienced missed or delayed alerts.
-Jayadev
We've confirmed that all systems are back to normal with no customer impact as of 04/05, 17:30 UTC. Our logs show the incident started on 04/05, 16:30 UTC and that during the 1 hour that it took to resolve the issue some customers using Log Search Alerts in multiple regions with running queries on tables that have no data and may have experienced missed or delayed alerts.
- Root Cause: The failure was due to issues with one of the backend services.
- Incident Timeline: 1 Hour - M/D, 04/05, 16:30 UTC through 04/05, 17:30 UTC
-Jayadev
Initial Update: Sunday, 05 April 2020 18:01 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customers in multiple regions may have experienced data access, missed or delayed alerts for Log Search Alerts.
-Jayadev
We are aware of issues within Log Search Alerts and are actively investigating. Some customers in multiple regions may have experienced data access, missed or delayed alerts for Log Search Alerts.
- Work Around: none
- Next Update: Before 04/05 22:30 UTC
-Jayadev