%3CLINGO-SUB%20id%3D%22lingo-sub-2117859%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2002%2F08%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2117859%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%20Monday%2C%2008%20February%202021%2017%3A05%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F08%2C%2015%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F08%2C%2014%3A20%20UTC%20and%20that%20during%20the%2070%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20experienced%20misfired%20log%20search%20alerts%20and%20possible%20latent%20ingestion.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20within%20compute%20resources%20after%20a%20backend%20update%20process%20completed%20which%20caused%20nodes%20to%20fail%20to%20initialize.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2010%20minutes%20-%2002%2F08%2C%2014%3A20%20UTC%20through%2002%2F08%2C%2015%3A30%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-Jeff%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2008%20February%202021%2015%3A08%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%26nbsp%3Bdata%20access%20issue%20in%20Azure%20Portal%20and%20issues%20with%20missed%20or%20delayed%20Log%20Search%20alerts%20in%20Canada%20Central%20region.%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%2002%2F08%2017%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Deepika%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-2117859%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 08 February 2021 17:05 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/08, 15:30 UTC. Our logs show the incident started on 02/08, 14:20 UTC and that during the 70 minutes that it took to resolve the issue customers experienced misfired log search alerts and possible latent ingestion.
  • Root Cause: The failure was due to an issue within compute resources after a backend update process completed which caused nodes to fail to initialize.
  • Incident Timeline: 1 Hour & 10 minutes - 02/08, 14:20 UTC through 02/08, 15:30 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jeff

Initial Update: Monday, 08 February 2021 15:08 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue in Azure Portal and issues with missed or delayed Log Search alerts in Canada Central region.
  • Work Around: NA
  • Next Update: Before 02/08 17:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Deepika