Azure Log Analytics experiencing data access issues in Australia East - 03/03 - Resolved

Published Mar 03 2022 08:03 AM 796 Views
Final Update: Thursday, 03 March 2022 16:57 UTC

We've confirmed that all systems are back to normal with no customer impact as of 3/3, 15:00 UTC. Our logs show the incident started on 3/3, 13:05 UTC and that during the 2 hours that it took to resolve the issue, customers using Azure Log Analytics in Australia East may have experienced data access issues as well as delayed or misfired alerts.
  • Root Cause: The failure was due to a backend storage resource that became unhealthy. 
  • Incident Timeline: 1 Hours & 55 minutes - 3/4, 13:05 UTC through 3/3, 15:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Ian

Update: Thursday, 03 March 2022 15:57 UTC

Customers using Azure Log Analytics and Azure Sentinel may experience data access issues as well as missed or delayed log search alerts in Australia East region.
  • Work Around: None
  • Next Update: Before 03/03 20:00 UTC
-Lokesh

%3CLINGO-SUB%20id%3D%22lingo-sub-3246161%22%20slang%3D%22en-US%22%3EAzure%20Log%20Analytics%20experiencing%20data%20access%20issues%20in%20Australia%20East%20-%2003%2F03%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3246161%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%20Thursday%2C%2003%20March%202022%2016%3A57%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%203%2F3%2C%2015%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%203%2F3%2C%2013%3A05%20UTC%20and%20that%20during%20the%202%20hours%20that%20it%20took%20to%20resolve%20the%20issue%2C%20customers%20using%20Azure%20Log%20Analytics%20in%20Australia%20East%20may%20have%20experienced%20data%20access%20issues%20as%20well%20as%20delayed%20or%20misfired%20alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20backend%20storage%20resource%20that%20became%20unhealthy.%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%2055%20minutes%20-%203%2F4%2C%2013%3A05%20UTC%20through%203%2F3%2C%2015%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-Ian%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%3EUpdate%3C%2FU%3E%3A%20Thursday%2C%2003%20March%202022%2015%3A57%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22color%3A%20rgb(36%2C%2036%2C%2036)%3B%20font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3ECustomers%20using%20Azure%20Log%20Analytics%20and%20Azure%20Sentinel%20may%20experience%20data%20access%20issues%20as%20well%20as%20missed%20or%20delayed%20log%20search%20alerts%20in%20Australia%20East%20region.%3C%2FSPAN%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%2003%2F03%2020%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Lokesh%3CBR%20%2F%3E%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
Version history
Last update:
‎Mar 03 2022 09:05 AM
Updated by: