Home
%3CLINGO-SUB%20id%3D%22lingo-sub-822005%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2008%2F25%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-822005%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Sunday%2C%2025%20August%202019%2018%3A56%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%208%2F25%2C%2018%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%208%2F25%2C%2016%3A30%20UTC%20and%20that%20during%20the%20incident%20c%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3Eustomers%20using%20Log%20Analytics%20in%20USGov%20Virginia%20may%20have%20received%20failure%20notifications%20-%20such%20as%20HTTP%20502%20Gateway%20Timeout%20or%20503%20Service%20Unavailable%20-%20when%20performing%20log%20search%20operations%20for%20data%20access.%20Alerting%20may%20have%20also%20been%20delayed.%20Tiles%20and%20blades%20may%20also%20have%20failed%20to%20load%20and%20display%20data%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3E.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3EPreliminary%20Root%20Cause%3A%20Engineers%20determined%20that%20instances%20of%20a%20backend%20service%20became%20unhealthy%2C%20preventing%20these%20requests%20from%20completing.%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3EMitigation%3A%20Engineers%20performed%20a%20manual%20restart%20of%20a%20backend%20service%20to%20mitigate%20the%20issue%3C%2FSPAN%3E%3C%2FDIV%3E%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-Azure%20Monitor%20SRE%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%20Sunday%2C%2025%20August%202019%2017%3A43%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20Data%20Access%20issues%20and%20Alerts%20may%20also%20be%20impacted%20in%20US%20national%20Cloud.%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%2008%2F25%2020%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Azure%20Monitor%20SRE%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-822005%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: Sunday, 25 August 2019 18:56 UTC

We've confirmed that all systems are back to normal with no customer impact as of 8/25, 18:00 UTC. Our logs show the incident started on 8/25, 16:30 UTC and that during the incident customers using Log Analytics in USGov Virginia may have received failure notifications - such as HTTP 502 Gateway Timeout or 503 Service Unavailable - when performing log search operations for data access. Alerting may have also been delayed. Tiles and blades may also have failed to load and display data.
  • Preliminary Root Cause: Engineers determined that instances of a backend service became unhealthy, preventing these requests from completing.
  • Mitigation: Engineers performed a manual restart of a backend service to mitigate the issue
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Azure Monitor SRE

Initial Update: Sunday, 25 August 2019 17:43 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience Data Access issues and Alerts may also be impacted in US national Cloud.
  • Work Around: None
  • Next Update: Before 08/25 20:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Azure Monitor SRE