%3CLINGO-SUB%20id%3D%22lingo-sub-1386211%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2005%2F13%20-%20Investigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1386211%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%3EInitial%20Update%3C%2FU%3E%3A%20Wednesday%2C%2013%20May%202020%2012%3A29%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20with%20Log%20Analytics%20saved%20searches%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20issues%20accessing%20data%20using%20saved%20searches.%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%2005%2F13%2016%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Santhosh%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1386211%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1393072%22%20slang%3D%22en-US%22%3ERe%3A%20Experiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2005%2F13%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1393072%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20what%20Azure%20regions%20were%20impacted%20by%20this%20issue%3F%20Please%20always%20list%20out%20the%20regions%20so%20customers%20can%20assess%20the%20blast%20radius%20quickly.%20Thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Final Update: Wednesday, 13 May 2020 20:10 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/13, 20:00 UTC. Our logs show the incident started on 05/12, 16:30 UTC and that during the 27 hours & 30 minutes that it took to resolve the issue some of the customers might have experienced data access issues while attempting to use saved searches.
  • Root Cause: The failure was due to an issue in one of our back-end services.
  • Incident Timeline: 27 Hours & 30 minutes - 05/12, 16:30 UTC through 05/13, 20:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Saika

Update: Wednesday, 13 May 2020 18:08 UTC

Root cause has been isolated to access data using saved searches which was impacting Log Analytics. To address this issue we fixed our back-end services. Data Access is now working as expected. Some of the customers may experience the data access issues and we estimate ~3 hours before all the impact is addressed.
  • Work Around: None
  • Next Update: Before 05/13 21:30 UTC
-Saika

Initial Update: Wednesday, 13 May 2020 12:29 UTC

We are aware of issues with Log Analytics saved searches and are actively investigating. Some customers may experience issues accessing data using saved searches.
  • Work Around: None
  • Next Update: Before 05/13 18:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.

-Santhosh

1 Comment
Senior Member

Hello, what Azure regions were impacted by this issue? Please always list out the regions so customers can assess the blast radius quickly. Thanks!