Home
%3CLINGO-SUB%20id%3D%22lingo-sub-682242%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2006%2F11%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-682242%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%2011%20June%202019%2006%3A51%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2006%2F11%2C%2006%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F11%2C%2003%3A10%20UTC%20and%20that%20during%20the%203%20hours%2020%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20issues%20accessing%20Log%20Search%20Alerts%20and%20Log%20Search%20queries%20via%20the%20Azure%20Portal..%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20performance%20degradation%20in%20one%20of%20our%20backend%20components.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2020%20minutes%20-%2006%2F11%2C%2003%3A10%20UTC%20through%2006%2F11%2C%2006%3A30%20UTC%3CBR%20%2F%3E%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-Mohini%20Nikam%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%2011%20June%202019%2004%3A29%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20difficulties%20accessing%20query%20logs%20from%20Azure%20portal.%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%2006%2F11%2008%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Mohini%20Nikam%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-682242%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 11 June 2019 06:51 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/11, 06:30 UTC. Our logs show the incident started on 06/11, 03:10 UTC and that during the 3 hours 20 minutes that it took to resolve the issue some customers may have experienced issues accessing Log Search Alerts and Log Search queries via the Azure Portal..
  • Root Cause: The failure was due to performance degradation in one of our backend components.
  • Incident Timeline: 3 Hours & 20 minutes - 06/11, 03:10 UTC through 06/11, 06:30 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Mohini Nikam

Initial Update: Tuesday, 11 June 2019 04:29 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience difficulties accessing query logs from Azure portal.
  • Work Around: None
  • Next Update: Before 06/11 08:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Mohini Nikam