Home
%3CLINGO-SUB%20id%3D%22lingo-sub-615893%22%20slang%3D%22en-US%22%3EExperiencing%20issue%20for%20Log%20Search%20Alerts%20and%20Azure%20UX%20(Log%20Search)%20in%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-615893%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Monday%2C%2020%20May%202019%2017%3A01%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2005%2F20%2C%2016%3A05%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2005%2F20%2C%2014%3A15%20UTC%20and%20that%20during%20the%201%20hour%20and%2050%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2065%25%20of%20customers%20in%20USGov%20Virginia%20region%20experienced%20log%20analytics%20data%20access%20issues%20including%20issues%20with%20log%20search%20alerts%20and%20log%20search%20queries%20in%20Azure%20portal.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20the%20dependency%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%2050%20minutes%20-%2005%2F20%2C%2014%3A15%20UTC%20through%2005%2F20%2C%2016%3A05%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Log%20Analytics%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Jayadev%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%20Monday%2C%2020%20May%202019%2016%3A16%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.%20Customers%20will%20not%20be%20receiving%20any%20log%20alerts%20for%20log%20search%20in%20Log%20Analytics%20for%20USGov%20Virginia%20region.%20Also%20Log%20Search%20page%20for%20Azure%20UX%20will%20be%20down%20when%20user%20inputs%20query.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2005%2F20%2019%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E-Jayadev%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-615893%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: Monday, 20 May 2019 17:01 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/20, 16:05 UTC. Our logs show the incident started on 05/20, 14:15 UTC and that during the 1 hour and 50 minutes that it took to resolve the issue 65% of customers in USGov Virginia region experienced log analytics data access issues including issues with log search alerts and log search queries in Azure portal.
  • Root Cause: The failure was due to one of the dependency services.
  • Incident Timeline: 1 Hours & 50 minutes - 05/20, 14:15 UTC through 05/20, 16:05 UTC
We understand that customers rely on Log Analytics as a critical service and apologize for any impact this incident caused.

-Jayadev

Initial Update: Monday, 20 May 2019 16:16 UTC

We are aware of issues within Log Analytics and are actively investigating. Customers will not be receiving any log alerts for log search in Log Analytics for USGov Virginia region. Also Log Search page for Azure UX will be down when user inputs query.
  • Next Update: Before 05/20 19:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.

-Jayadev