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

Published Mar 04 2021 06:53 AM 1,176 Views
Final Update: Thursday, 04 March 2021 20:55 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/04, 20:25 UTC. Our logs show the incident started on 03/04, 14:08 UTC and that during the 6 hours & 17 minutes that it took to resolve the issue some customers may experience data access issues and missed or delayed alerts in WestUS2 region.
  • Root Cause: We determined that there was a limited number of nodes that had reached an operational threshold causing these intermittent issues with accessing your data as well as the missing or delayed alerts.
  • Incident Timeline: 6 Hours & 17 minutes - 03/04, 14:08 UTC through 03/04, 20:25 UTC.
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Vincent

Update: Thursday, 04 March 2021 17:36 UTC

We continue to investigate issues within Log Analytics. Some customers continue to experience Data access issues and missed or delayed alerts in WestUS2 region.Initial findings indicate that the problem began at 03/04 16:08 UTC. We are working with our backend team to fix this issue. 
  • Next Update: Before 03/04 22:00 UTC
-Jayadev

Initial Update: Thursday, 04 March 2021 14:50 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience Data access issues and missed or delayed alerts in WestUS2 region.
  • Work Around: None
  • Next Update: Before 03/04 17:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Vyom

%3CLINGO-SUB%20id%3D%22lingo-sub-2184907%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2003%2F04%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2184907%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%20Thursday%2C%2004%20March%202021%2020%3A55%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%2F04%2C%2020%3A25%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F04%2C%2014%3A08%20UTC%20and%20that%20during%20the%206%20hours%20%26amp%3B%2017%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20experience%20data%20access%20issues%20and%20missed%20or%20delayed%20alerts%20in%20WestUS2%20region.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CUL%20style%3D%22%22%3E%3CLI%20style%3D%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3ERoot%20Cause%3C%2FU%3E%3A%20We%20determined%20that%20there%20was%20a%20limited%20number%20of%20nodes%20that%20had%20reached%20an%20operational%20threshold%20causing%20these%20intermittent%20issues%20with%20accessing%20your%20data%20as%20well%20as%20the%20missing%20or%20delayed%20alerts.%3CBR%20%2F%3E%3C%2FLI%3E%3CLI%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%206%20Hours%20%26amp%3B%2017%20minutes%20-%2003%2F04%2C%2014%3A08%20UTC%20through%2003%2F04%2C%2020%3A25%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-Vincent%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%20Thursday%2C%2004%20March%202021%2017%3A36%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Some%20customers%20continue%20to%20experience%20Data%20access%20issues%20and%20missed%20or%20delayed%20alerts%20in%20WestUS2%20region.Initial%20findings%20indicate%20that%20the%20problem%20began%20at%2003%2F04%2016%3A08%20UTC.%20We%20are%20working%20with%20our%20backend%20team%20to%20fix%20this%20issue.%26nbsp%3B%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2003%2F04%2022%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Jayadev%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%20Thursday%2C%2004%20March%202021%2014%3A50%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%20issues%20and%20missed%20or%20delayed%20alerts%20in%20WestUS2%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%2F04%2017%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Vyom%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2184907%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 04 2021 04:00 PM
Updated by: