This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Saturday, 01 February 2020 00:44 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/31, 22:56 UTC. Our logs show the incident started on 01/31, 20:30 UTC and that during the 2 hours 26 minutes that it took to resolve the issue some customers might have experienced issues while querying data or might have seen failures related to log search alerts.
We've confirmed that all systems are back to normal with no customer impact as of 01/31, 22:56 UTC. Our logs show the incident started on 01/31, 20:30 UTC and that during the 2 hours 26 minutes that it took to resolve the issue some customers might have experienced issues while querying data or might have seen failures related to log search alerts.
- Root Cause: The failure was due to .recent configuration change on a dependent service was causing down stream impact to the service.
- Incident Timeline: 2 Hours & 26 minutes - 01/31, 20:30 UTC through 01/31, 22:56 UTC
-Subhash
Initial Update: Friday, 31 January 2020 22:15 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers in West US may experience issues with Data access from Azure portal , query failures in Log Analytics and delayed or missed alerts in Log search alerts.
-Subhash
We are aware of issues within Log Analytics and are actively investigating. Some customers in West US may experience issues with Data access from Azure portal , query failures in Log Analytics and delayed or missed alerts in Log search alerts.
- Work Around:
- Next Update: Before 02/01 02:30 UTC
-Subhash