%3CLINGO-SUB%20id%3D%22lingo-sub-1642155%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20and%20Alerting%20Issues%20for%20Appplication%20Insights%20and%20Log%20Analytics%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1642155%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%2007%20September%202020%2020%3A18%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%2F07%2C%2020%3A27%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2009%2F07%2C17%3A00%20UTC%20and%20that%20during%20the%203%20hours%20and%2027%20minutes%20that%20it%20took%20to%20mitigate%20the%20issue%2C%20a%20subset%20of%20customers%20using%20Azure%20monitor%20services%20such%20as%20Application%20Insights%2C%20Log%20Analytics%20and%2For%20Log%20Search%20Alerts%20may%20have%20experienced%20issues%20with%20data%20access%2C%20alerting%20failures%20%2F%20missed%20alerts%20and%20UI%20loading%20issues%20when%20running%20queries%20from%20portal.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20deployment%20for%20one%20of%20the%20backend%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2027%20minutes%20-%2009%2F07%2C%2017%3A00%20UTC%20through%2009%2F07%2C%2020%3A27%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%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%2007%20September%202020%2017%3A59%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20Data%20Access%20issues%2C%20alerting%20failures%20or%20missed%20alerts%20and%20UI%20loading%20issues%20when%20querying%20from%20portal.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2009%2F07%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-1642155%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%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, 07 September 2020 20:18 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/07, 20:27 UTC. Our logs show the incident started on 09/07,17:00 UTC and that during the 3 hours and 27 minutes that it took to mitigate the issue, a subset of customers using Azure monitor services such as Application Insights, Log Analytics and/or Log Search Alerts may have experienced issues with data access, alerting failures / missed alerts and UI loading issues when running queries from portal.
  • Root Cause: The failure was due to a deployment for one of the backend services.
  • Incident Timeline: 3 Hours & 27 minutes - 09/07, 17:00 UTC through 09/07, 20:27 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Jayadev

Initial Update: Monday, 07 September 2020 17:59 UTC

We are aware of issues within Application Insights and Log Analytics and are actively investigating. Some customers may experience Data Access issues, alerting failures or missed alerts and UI loading issues when querying from portal.
  • Next Update: Before 09/07 22:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jayadev