Home
%3CLINGO-SUB%20id%3D%22lingo-sub-915118%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2010%2F15%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-915118%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Tuesday%2C%2015%20October%202019%2011%3A41%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2010%2F15%2C%2010%3A45%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F15%2C%2009%3A15%20UTC%20and%20that%20during%20the%201%20hour%20and%2030%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20~6%25%20of%20the%20customers%20might%20experienced%20issues%20with%20data%20access%20in%20West%20Europe%20region%20for%20Log%20Analytics%20and%20also%20issues%20with%20Log%20Alerts%20not%20being%20triggered%20as%20expected.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%26nbsp%3B1%20Hours%20%26amp%3B%26nbsp%3B30%20minutes%20-%2010%2F15%2C%2009%3A15%20UTC%20through10%2F15%2C%2010%3A45UTC%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-Anmol%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3A%20lightgray%3B%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Tuesday%2C%2015%20October%202019%2010%3A13%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20alerting%20failures%20and%20data%20access%20issues%20for%20Azure%20Log%20Analytics%20in%20West%20Europe%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%2010%2F15%2012%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Anmol%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3A%20lightgray%3B%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-915118%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 15 October 2019 11:41 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/15, 10:45 UTC. Our logs show the incident started on 10/15, 09:15 UTC and that during the 1 hour and 30 minutes that it took to resolve the issue ~6% of the customers might experienced issues with data access in West Europe region for Log Analytics and also issues with Log Alerts not being triggered as expected.
  • Root Cause: The failure was due to an issue in one of our dependent service.
  • Incident Timeline: 1 Hours & 30 minutes - 10/15, 09:15 UTC through10/15, 10:45UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Anmol

Initial Update: Tuesday, 15 October 2019 10:13 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience alerting failures and data access issues for Azure Log Analytics in West Europe region.
  • Work Around: None
  • Next Update: Before 10/15 12:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anmol