Home
%3CLINGO-SUB%20id%3D%22lingo-sub-854793%22%20slang%3D%22en-US%22%3EExperiencing%20issue%20for%20Log%20Analytics%20service%20for%20data%20access%20and%20alerting%20in%20West%20US2%20Region%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-854793%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%20Friday%2C%2013%20September%202019%2018%3A47%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2009%2F13%2C%2018%3A03%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2009%2F13%2C%2016%3A55%20UTC%20and%20that%20during%20the%201%20hour%20and%208%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2031%25%20of%20customers%20experienced%20issue%20with%20data%20access%20and%20alerting%20for%20workspaces%20in%20West%20US2%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20the%20backend%20dependent%20service%20.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%208%20minutes%20-%2009%2F13%2C%2016%3A55%20UTC%20through%2009%2F13%2C%2018%3A03%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-Subhash%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Friday%2C%2013%20September%202019%2017%3A56%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20issue%20with%20data%20access%20and%20alerting%20for%20workspaces%20in%20West%20US2%20region.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2009%2F13%2022%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jayadev%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-854793%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: Friday, 13 September 2019 18:47 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/13, 18:03 UTC. Our logs show the incident started on 09/13, 16:55 UTC and that during the 1 hour and 8 minutes that it took to resolve the issue 31% of customers experienced issue with data access and alerting for workspaces in West US2 region.
  • Root Cause: The failure was due to one of the backend dependent service .
  • Incident Timeline: 1 Hours & 8 minutes - 09/13, 16:55 UTC through 09/13, 18:03 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Subhash

Initial Update: Friday, 13 September 2019 17:56 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issue with data access and alerting for workspaces in West US2 region.
  • Next Update: Before 09/13 22:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jayadev