Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1005099%22%20slang%3D%22en-US%22%3ERe%3A%20Experiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2011%2F13%20-%20Investigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1005099%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20been%20experiencing%20Log%20Analytics%20problems%20almost%20daily%20for%20the%20last%20few%20weeks.%20Response%20times%20have%20always%20fluctuated%20(few%20ms%20to%20several%20secs)%2C%20but%20lately%20quite%20often%20queries%20time%20out%20or%2C%20like%20right%20now%2C%20result%20in%20a%20BadRequest%20(query%20error).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20persisting%20problem%20that%20keeps%20causing%20these%20issues%3F%20Can%20we%20expect%20things%20to%20stabilize%20soon%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3ERobert%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1004886%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2011%2F13%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1004886%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%20Wednesday%2C%2013%20November%202019%2016%3A10%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2011%2F13%2C%2011%3A25%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2011%2F13%2C%2010%3A10%20UTC%20and%20that%20during%20the%201%20hour%20and%2015%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20in%20West%20Europe%20region%20might%20have%20experienced%20Alerting%20failure%20or%20Data%20Latency%20issue.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20failure%20in%20one%20of%20out%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2015%20minutes%20-%2011%2F13%2C%2010%3A10%20UTC%20through%2011%2F13%2C%2011%3A15%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-Madhuri%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%20Wednesday%2C%2013%20November%202019%2011%3A27%20UTC%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20Data%20Access%20issues%20while%20accessing%20Log%20Analytics%20in%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%2011%2F13%2013%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Anusha%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-1004886%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 13 November 2019 16:10 UTC

We've confirmed that all systems are back to normal with no customer impact as of 11/13, 11:25 UTC. Our logs show the incident started on 11/13, 10:10 UTC and that during the 1 hour and 15 minutes that it took to resolve the issue customers in West Europe region might have experienced Alerting failure or Data Latency issue.
  • Root Cause: The failure was due to failure in one of out dependent services.
  • Incident Timeline: 1 Hour & 15 minutes - 11/13, 10:10 UTC through 11/13, 11:15 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Madhuri

Initial Update: Wednesday, 13 November 2019 11:27 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience Data Access issues while accessing Log Analytics in azure portal.
  • Work Around: None
  • Next Update: Before 11/13 13:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anusha

1 Comment
Occasional Visitor

We have been experiencing Log Analytics problems almost daily for the last few weeks. Response times have always fluctuated (few ms to several secs), but lately quite often queries time out or, like right now, result in a BadRequest (query error).

 

Is there a persisting problem that keeps causing these issues? Can we expect things to stabilize soon?

 

Regards,

Robert