Final Update: Monday, 24 June 2019 05:04 UTC
We've confirmed that all systems are back to normal with no customer impact as of 6/24, 04:54 UTC. Our logs show the incident started on 6/23, 22:50 UTC and that during the 6 hours and 4 minutes that it took to resolve the issue 2,588 customers experienced an inability to query their Log Analytics data and possible alert malfunctions.
-Jeff
We've confirmed that all systems are back to normal with no customer impact as of 6/24, 04:54 UTC. Our logs show the incident started on 6/23, 22:50 UTC and that during the 6 hours and 4 minutes that it took to resolve the issue 2,588 customers experienced an inability to query their Log Analytics data and possible alert malfunctions.
- Root Cause: The failure was due to a configuration change on the backend.
- Incident Timeline: 6 Hours & 4 minutes - 6/23, 22:50 UTC through 6/24, 04:54 UTC
-Jeff
Update: Monday, 24 June 2019 04:49 UTC
Root cause has been isolated to an incorrect configuration on the backend which was impacting query times. To address this issue we have applied an update to the configuration. We see queries now succeeding.
Root cause has been isolated to an incorrect configuration on the backend which was impacting query times. To address this issue we have applied an update to the configuration. We see queries now succeeding.
- Next Update: Before 06/24 06:00 UTC
Update: Monday, 24 June 2019 03:59 UTC
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience errors when searching and possible misbehaving alerts. We are working to establish the start time for the issue, initial findings indicate that the problem began at 06/23 22:50 UTC. We currently have no estimate for resolution.
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience errors when searching and possible misbehaving alerts. We are working to establish the start time for the issue, initial findings indicate that the problem began at 06/23 22:50 UTC. We currently have no estimate for resolution.
- Work Around: None
- Next Update: Before 06/24 06:00 UTC
Initial Update: Monday, 24 June 2019 02:15 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers in East Japan may experience issues querying data and alerts may be misfiring.
-Jeff
We are aware of issues within Log Analytics and are actively investigating. Some customers in East Japan may experience issues querying data and alerts may be misfiring.
- Work Around: none
- Next Update: Before 06/24 04:30 UTC
-Jeff
Updated Jun 23, 2019
Version 5.0