This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Thursday, 17 October 2019 12:12 UTC
We've confirmed that all systems are back to normal with no customer impact as of 10/17, 11:00 UTC. Our logs show the incident started on 10/15, 10:05 UTC and that during the 55 minutes that it took to resolve the issue ~7% of the customers might experienced issues with data access in West Europe region for Log Analytics and also issues with Log Alerts not being triggered as expected.
-Anmol
We've confirmed that all systems are back to normal with no customer impact as of 10/17, 11:00 UTC. Our logs show the incident started on 10/15, 10:05 UTC and that during the 55 minutes that it took to resolve the issue ~7% of the customers might experienced issues with data access in West Europe region for Log Analytics and also issues with Log Alerts not being triggered as expected.
- Root Cause: The failure was due to an issue in one of our backend service.
- Incident Timeline: 55 minutes - 10/17, 10:55 UTC through 10/17, 11:00 UTC
-Anmol
Initial Update: Thursday, 17 October 2019 11:10 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience alerting failures and data access issues for Azure Log Analytics in West Europe region.
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience alerting failures and data access issues for Azure Log Analytics in West Europe region.
- Work Around: None
- Next Update: Before 10/17 13:30 UTC
Anmol