Final Update: Wednesday, 07 February 2018 04:30 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/07, 03:30 UTC. Our logs show the incident started on 02/07, 02:00 UTC and that during the 1.5 hours that it took to resolve the issue some of customers would have experienced failures in Azure log Analytics services.
We've confirmed that all systems are back to normal with no customer impact as of 02/07, 03:30 UTC. Our logs show the incident started on 02/07, 02:00 UTC and that during the 1.5 hours that it took to resolve the issue some of customers would have experienced failures in Azure log Analytics services.
- Root Cause: The failure was due to configuration change in our services.
- Incident Timeline: 1 Hour & 30 minutes - 02/07, 02:00 UTC through 02/07, 03:30 UTC
We understand that customers rely on Azure Log Analytics Service as a critical service and apologize for any impact this incident caused.
Update: Wednesday, 07 February 2018 03:04 UTC
We continue to investigate issues within Azure Monitoring Services.. Root cause is not fully understood at this time. Customers may experience data access issue while using Azure Log Analytics services in Azure and OMS portal. We are working to establish the start time for the issue, initial findings indicate that the problem began at 02/07 ~02:00 UTC. We currently have no estimate for resolution.
We continue to investigate issues within Azure Monitoring Services.. Root cause is not fully understood at this time. Customers may experience data access issue while using Azure Log Analytics services in Azure and OMS portal. We are working to establish the start time for the issue, initial findings indicate that the problem began at 02/07 ~02:00 UTC. We currently have no estimate for resolution.
- Work Around: none
- Next Update: Before 02/07 05:30 UTC
-Arvind