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

Published Apr 27 2021 12:05 AM 722 Views
Final Update: Tuesday, 27 April 2021 08:11 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/27, 06:40 UTC. Our logs show the incident started on 04/27, 06:05 UTC and that during the 35 minutes that it took to resolve the issue some customers may have experienced issues with data access and delayed or missed Log Search Alerts in West US Region.
  • Root Cause: The failure was due to operational threshold on one of our backend services.
  • Incident Timeline: 35 minutes - 04/27, 06:05 UTC through 04/27, 06:40 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Soumyajeet

Initial Update: Tuesday, 27 April 2021 07:04 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issues and delayed or missed Log Search Alerts in West US region.
  • Work Around: None
  • Next Update: Before 04/27 09:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Soumyajeet

%3CLINGO-SUB%20id%3D%22lingo-sub-2296329%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2004%2F27%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2296329%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%2027%20April%202021%2008%3A11%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2004%2F27%2C%2006%3A40%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2004%2F27%2C%2006%3A05%20UTC%20and%20that%20during%20the%2035%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20issues%20with%20data%20access%20and%20delayed%20or%20missed%20Log%20Search%20Alerts%20in%20West%20US%20Region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20operational%20threshold%20on%20one%20of%20our%20backend%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2035%20minutes%20-%2004%2F27%2C%2006%3A05%20UTC%20through%2004%2F27%2C%2006%3A40%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-Soumyajeet%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%20Tuesday%2C%2027%20April%202021%2007%3A04%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%20delayed%20or%20missed%20Log%20Search%20Alerts%20in%20West%20US%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%2004%2F27%2009%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Soumyajeet%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:
‎Apr 27 2021 01:16 AM
Updated by: