This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Monday, 06 January 2020 20:19 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/06, 19:35 UTC. Our logs show the incident started on 01/06, 17:04 UTC and that during the 2 hours and 31 minutes that it took to resolve the issue some customers in Canada Central Region experienced issues with data access in Log Analytics and alerting failures or delayed alerts for Log Search Alerts.
-Jayadev
We've confirmed that all systems are back to normal with no customer impact as of 01/06, 19:35 UTC. Our logs show the incident started on 01/06, 17:04 UTC and that during the 2 hours and 31 minutes that it took to resolve the issue some customers in Canada Central Region experienced issues with data access in Log Analytics and alerting failures or delayed alerts for Log Search Alerts.
- Root Cause: The failure was due to issue in one of the backend services.
- Incident Timeline: 2 Hours & 31 minutes - 01/06, 17:04 UTC through 01/06, 19:35 UTC
-Jayadev
Update: Monday, 06 January 2020 18:40 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers in Canada Central Region may experience issues with data access in Log Analytics and alerting failures or delayed alerts for Log Search Alerts.
We are aware of issues within Log Analytics and are actively investigating. Some customers in Canada Central Region may experience issues with data access in Log Analytics and alerting failures or delayed alerts for Log Search Alerts.
- Work Around:
- Next Update: Before 01/06 23:00 UTC