This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Tuesday, 19 November 2019 08:24 UTC
We've confirmed that all systems are back to normal with no customer impact as of 11/19, 08:15 UTC. Our logs show the incident started on 11/19, 06:15 UTC and that during the 2 hours that it took to resolve the issue customers using Log Analytics may have experienced failures and timeouts while accessing workspaces and may also have experienced alerting failures in West Europe region.
-Rama
We've confirmed that all systems are back to normal with no customer impact as of 11/19, 08:15 UTC. Our logs show the incident started on 11/19, 06:15 UTC and that during the 2 hours that it took to resolve the issue customers using Log Analytics may have experienced failures and timeouts while accessing workspaces and may also have experienced alerting failures in West Europe region.
- Root Cause: The failure was due to issue with one of our backend service which became unhealthy.
- Incident Timeline: 2 Hours - 11/19, 06:15 UTC through 11/19, 08:15 UTC
-Rama
Initial Update: Tuesday, 19 November 2019 07:31 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue while using Azure portal and Alerting failure in West Europe region.
-Rama
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue while using Azure portal and Alerting failure in West Europe region.
- Work Around: None
- Next Update: Before 11/19 12:00 UTC
-Rama