Experiencing Data Access Issue in Azure portal for Log Analytics - 07/30 - Resolved

Published Jul 30 2021 03:01 AM 1,290 Views
Final Update: Friday, 30 July 2021 11:08 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/30, 08:55 UTC. Our logs show the incident started on  07/30, 08:20 UTC and that during the 35 minutes that it took to resolve the issue.
Some customers may have experienced data access issue and issues with missed or delayed Log Search alerts in Japan East region. 
  • Root Cause: The failure was due to an issue with one of the dependent services.
  • Incident Timeline: 35 minutes - 07/30, 08:20 UTC through 07/30, 08:55 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Vyom

Initial Update: Friday, 30 July 2021 09:52 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue and issues with missed or delayed Log Search alerts in Japan East region. Currently issue seems to be mitigated but we are still verifying.
  • Work Around: None.
  • Next Update: Before 07/30 13:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Vyom

%3CLINGO-SUB%20id%3D%22lingo-sub-2596033%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2007%2F30%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2596033%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Friday%2C%2030%20July%202021%2011%3A08%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2007%2F30%2C%2008%3A55%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%26nbsp%3B%26nbsp%3B07%2F30%2C%2008%3A20%20UTC%26nbsp%3Band%20that%20during%20the%2035%20minutes%20that%20it%20took%20to%20resolve%20the%20issue.%20%3C%2FSPAN%3ESome%20customers%20may%20have%20experienced%20data%20access%20issue%20and%20issues%20with%20missed%20or%20delayed%20Log%20Search%20alerts%20in%20Japan%20East%20region.%26nbsp%3B%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20with%20one%20of%20the%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2035%20minutes%20-%2007%2F30%2C%2008%3A20%20UTC%20through%2007%2F30%2C%2008%3A55%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-Vyom%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%20Friday%2C%2030%20July%202021%2009%3A52%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%20issues%20with%20missed%20or%20delayed%20Log%20Search%20alerts%20in%20Japan%20East%20region.%20Currently%20issue%20seems%20to%20be%20mitigated%20but%20we%20are%20still%20verifying.%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%2007%2F30%2013%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%2FLINGO-BODY%3E
Version history
Last update:
‎Jul 30 2021 04:18 AM
Updated by:
www.000webhost.com