Experiencing Data Access Issue in Azure portal for Log Analytics - 01/18 - Resolved

Published Jan 18 2022 07:24 AM 647 Views
Final Update: Tuesday, 18 January 2022 15:16 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/18, 13:30 UTC. Our logs show the incident started on 01/18, 13:00 UTC and that during the 30 minutes that it took to resolve the issue some of the customers using Log Analytics or Azure Sentinel in South UK region may have experienced issues accessing data as well as missed or delayed Log Search alerts.
  • Root Cause: We determined that instances of a backend service became unhealthy, preventing these requests from completing.
  • Incident Timeline: 30 minutes - 01/18, 13:00 UTC through 01/18, 13:30 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Surya 
%3CLINGO-SUB%20id%3D%22lingo-sub-3064673%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2001%2F18%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3064673%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%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%2018%20January%202022%2015%3A16%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%2001%2F18%2C%2013%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F18%2C%2013%3A00%20UTC%20and%20that%20during%20the%2030%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%26nbsp%3B%3C%2FSPAN%3Esome%20of%20the%20customers%20using%20Log%20Analytics%20or%20Azure%20Sentinel%20in%20South%20UK%20region%20may%20have%20experienced%20issues%20accessing%20data%20as%20well%20as%20missed%20or%20delayed%20Log%20Search%20alerts.%3CBR%20%2F%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20We%20determined%20that%20instances%20of%20a%20backend%20service%20became%20unhealthy%2C%20preventing%20these%20requests%20from%20completing.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2030%20minutes%20-%2001%2F18%2C%2013%3A00%20UTC%20through%2001%2F18%2C%2013%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%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E-Surya%26nbsp%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jan 18 2022 08:24 AM
Updated by: