Experiencing Data Access Issue in Azure portal for Log Analytics - 11/02 - Resolved

Published Nov 02 2021 07:16 AM 1,362 Views
Final Update: Tuesday, 02 November 2021 15:20 UTC

We've confirmed that all systems are back to normal with no customer impact as of 11/02, 14:30 UTC. Our logs show the incident started on 11/02, 12:40 UTC and that during the 1 hour and 50 minutes that it took to resolve the issue. Customers using Azure Log Analytics and/or Sentinel in Australia South East who may have experienced intermittent query failures and delayed or missed alerts
  • Root Cause: The failure was due to a recent deployment task impacted instances of a backend service which became unhealthy, preventing requests from completing.
  • Incident Timeline: 1 Hour & 50 minutes - 11/02, 12:40 UTC through 11/02, 14:30 UTC
We understand that customers rely on Azure Log Analytics and/or Sentinel as a critical service and apologize for any impact this incident caused.

-Mohsin Inamdar

Update: Tuesday, 02 November 2021 14:09 UTC

We continue to investigate issues within Log Analytics and/or Sentinel. Root cause is not fully understood at this time. Some customers continue to experience  intermittent query failures, delayed or missed alerts. We are working to establish the start time for the issue, initial findings indicate that the problem began at <11/02 ~12:40 UTC>. We currently have no estimate for resolution.
  • Work Around: NA
  • Next Update: Before 11/02 17:30 UTC
-Mohsin Inamdar

%3CLINGO-SUB%20id%3D%22lingo-sub-2914267%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2011%2F02%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2914267%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EFinal%20Update%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3A%20Tuesday%2C%2002%20November%202021%2015%3A20%20UTC%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2011%2F02%2C%2014%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2011%2F02%2C%2012%3A40%20UTC%20and%20that%20during%20the%201%20hour%20and%2050%20minutes%20that%20it%20took%20to%20resolve%20the%20issue.%20C%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3Eustomers%20using%20Azure%20Log%20Analytics%20and%2For%20Sentinel%20in%20Australia%20South%20East%20who%20may%20have%20experienced%20intermittent%20query%20failures%20and%20delayed%20or%20missed%20alerts%3C%2FSPAN%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20recent%20deployment%20task%20impacted%20instances%20of%20a%20backend%20service%20which%20became%20unhealthy%2C%20preventing%20requests%20from%20completing.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2050%20minutes%20-%2011%2F02%2C%2012%3A40%20UTC%20through%2011%2F02%2C%2014%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3Eand%2For%20Sentinel%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3Eas%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E-Mohsin%20Inamdar%3C%2FSPAN%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EUpdate%3C%2FU%3E%3A%20Tuesday%2C%2002%20November%202021%2014%3A09%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics%20and%2For%20Sentinel.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20continue%20to%20experience%26nbsp%3B%20intermittent%20query%20failures%2C%20delayed%20or%20missed%20alerts.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%20%26lt%3B11%2F02%20~12%3A40%20UTC%26gt%3B.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20NA%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2011%2F02%2017%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Mohsin%20Inamdar%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Nov 02 2021 08:34 AM
Updated by: