Experiencing Data Access Issue in Azure portal for Log Analytics - 08/09 - Resolved

Published Aug 09 2021 12:27 PM 1,610 Views
Final Update: Monday, 09 August 2021 21:35 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/09, 20:00 UTC. Our logs show the incident started on 08/09, 17:00 UTC and that during the 3 hours that it took to resolve the issue, A subset of customers may have experienced delayed or missed Log Search Alerts and Metric Alerts on Log Analytics metrics. Customers may also see some data latency.
  • Root Cause: The failure was due to a bad configuration.
  • Incident Timeline: 3 Hours - 08/09, 17:00 UTC through 08/09, 20:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Eric Singleton

Initial Update: Monday, 09 August 2021 19:17 UTC

We are aware of issues within Log Analytics and are actively investigating. A subset of customers may experience delayed or missed Log Search Alerts and metric Alerts on Log analytics metrics. Customers may also see some data latency.

  • Work Around: none
  • Next Update: Before 08/09 23:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Eric Singleton

%3CLINGO-SUB%20id%3D%22lingo-sub-2628958%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2008%2F09%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2628958%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%20Monday%2C%2009%20August%202021%2021%3A35%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2008%2F09%2C%2020%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F09%2C%2017%3A00%20UTC%20and%20that%20during%20the%203%20hours%20that%20it%20took%20to%20resolve%20the%20issue%2C%20A%20subset%20of%20customers%20may%20have%20experienced%20delayed%20or%20missed%20Log%20Search%20Alerts%20and%20Metric%20Alerts%20on%20Log%20Analytics%20metrics.%20Customers%20may%20also%20see%20some%20data%20latency.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20bad%20configuration.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20-%2008%2F09%2C%2017%3A00%20UTC%20through%2008%2F09%2C%2020%3A00%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-Eric%20Singleton%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%2009%20August%202021%2019%3A17%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20A%20subset%20of%20customers%20may%20experience%20delayed%20or%20missed%20Log%20Search%20Alerts%20and%20metric%20Alerts%20on%20Log%20analytics%20metrics.%20Customers%20may%20also%20see%20some%20data%20latency.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%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%2F09%2023%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Eric%20Singleton%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Aug 09 2021 02:41 PM
Updated by: