Experiencing Data Access Issue in Azure portal for Log Analytics - 03/31 - Resolved

Published Apr 06 2021 11:37 AM 562 Views
Final Update: Wednesday, 31 March 2021 14:17 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/31, 14:00 UTC. Our logs show the incident started on 03/31, 12:05 UTC and that during the 1 Hour & 55 minutes that it took to resolve the issue some customers may have experienced data access issue and delayed or missed alerts in East US 2 region.                              
  • Root Cause: The failure was due to issues with one of our dependent service.
  • Incident Timeline: 1 Hour & 55 minutes - 03/31, 12:05 UTC through 03/31, 14:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Harshita

Initial Update: Wednesday, 31 March 2021 13:03 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue and delayed or missed alerts in East US 2 region.
  • Work Around: None
  • Next Update: Before 03/31 16:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Harshita

%3CLINGO-SUB%20id%3D%22lingo-sub-2246882%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2003%2F31%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2246882%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%20Wednesday%2C%2031%20March%202021%2014%3A17%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2003%2F31%2C%2014%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F31%2C%2012%3A05%26nbsp%3BUTC%20and%20that%20during%20the%201%20Hour%20%26amp%3B%2055%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20data%20access%20issue%20and%20delayed%20or%20missed%20alerts%20in%20East%20US%202%20region.%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20with%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2055%20minutes%20-%2003%2F31%2C%2012%3A05%26nbsp%3BUTC%20through%2003%2F31%2C%2014%3A00%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-Harshita%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%3EInitial%20Update%3C%2FU%3E%3A%20Wednesday%2C%2031%20March%202021%2013%3A03%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20data%20access%20issue%20and%26nbsp%3Bdelayed%20or%20missed%20alerts%20in%20East%20US%202%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2003%2F31%2016%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Harshita%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2246882%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Mar 31 2021 07:26 AM
Updated by: