Experiencing Data Access Issue in Azure portal for Log Analytics - 05/24 - Resolved

Published May 24 2022 05:21 AM 594 Views
Final Update: Tuesday, 24 May 2022 12:16 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/24, 11:52 UTC. Our logs show the incident started on 05/24, 11:23 UTC and that during the 29 minutes that it took to resolve the issue some of the customers using Log Analytics may have experienced data access issue and delayed or missed alerts in West Europe region. Some customers using Azure Sentinel may also experience data access issues and delayed or misfired alerts.
  • Root Cause: The failure was due to one of our backend service.
  • Incident Timeline: 29 minutes - 05/24, 11:23 UTC through 05/24, 11:52 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Deepika

%3CLINGO-SUB%20id%3D%22lingo-sub-3420325%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2005%2F24%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3420325%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%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Tuesday%2C%2024%20May%202022%2012%3A16%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2005%2F24%2C%2011%3A52%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2005%2F24%2C%2011%3A23%20UTC%20and%20that%20during%20the%2029%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%26nbsp%3Bsome%20of%20the%20customers%20using%20Log%20Analytics%20may%20have%20experienced%20data%20access%20issue%20and%20delayed%20or%20missed%20alerts%20in%20West%20Europe%20region.%20Some%20customers%20using%20Azure%20Sentinel%20may%20also%20experience%20data%20access%20issues%20and%20delayed%20or%20misfired%20alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20our%20backend%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2029%20minutes%20-%2005%2F24%2C%2011%3A23%20UTC%20through%2005%2F24%2C%2011%3A52%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Deepika%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎May 24 2022 05:21 AM
Updated by: