Experiencing Data Latency for Log Analytics - 10/23 - Resolved

Published Oct 22 2021 07:24 PM 1,351 Views
Final Update: Saturday, 23 October 2021 05:19 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/23, 05:05 UTC. Our logs show the incident started on 10/22, 22:30 UTC and that during the 6 hours & 35 minutes that it took to resolve the issue some customers may have experienced intermittent data latency, partial query result and incorrect alert activation in West US 2 region.
  • Root Cause: The failure was due to an issue with dependent service.
  • Incident Timeline: 6 Hours & 35 minutes - 10/22, 22:30 UTC through 10/23, 05:05 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Vyom

Update: Saturday, 23 October 2021 02:23 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. 
Customers ingesting telemetry in their Log Analytics Workspace in West US 2 geographical region during 10/22 starting from 22:30 UTC may have experienced intermittent data latency, partial query result and incorrect alert activation
  • Work Around: none
  • Next Update: Before 10/23 05:30 UTC
-Varun

%3CLINGO-SUB%20id%3D%22lingo-sub-2876208%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20for%20Log%20Analytics%20-%2010%2F23%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2876208%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%20Saturday%2C%2023%20October%202021%2005%3A19%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2010%2F23%2C%2005%3A05%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2010%2F22%2C%2022%3A30%20UTC%20and%20that%20during%20the%206%20hours%20%26amp%3B%2035%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20intermittent%20data%20latency%2C%20partial%20query%20result%20and%20incorrect%20alert%20activation%20in%20West%20US%202%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20with%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%206%20Hours%20%26amp%3B%2035%20minutes%20-%2010%2F22%2C%2022%3A30%20UTC%20through%2010%2F23%2C%2005%3A05%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-Vyom%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%20Saturday%2C%2023%20October%202021%2002%3A23%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%26nbsp%3B%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%3ECustomers%20ingesting%20telemetry%20in%20their%20Log%20Analytics%20Workspace%20in%20West%20US%202%20geographical%20region%20during%2010%2F22%20starting%20from%2022%3A30%20UTC%20may%20have%20experienced%20intermittent%20data%20latency%2C%20partial%20query%20result%20and%20incorrect%20alert%20activation%3C%2FDIV%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%2010%2F23%2005%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Varun%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%2FLINGO-BODY%3E
Version history
Last update:
‎Oct 22 2021 10:23 PM
Updated by: