Experiencing Data Latency for Log Analytics - 03/24 - Resolved

Published Mar 23 2022 06:38 PM 1,085 Views
Final Update: Thursday, 24 March 2022 02:35 UTC

We've confirmed that all systems are back to normal with no customer impact as of 3/24, 02:32 UTC. Our logs show the incident started on 3/23, 23:25 UTC and that during the 3 hours and 7 minutes that it took to resolve the issue customers may experience up to 2 hours of ingestion latency and missed or delayed Log Search Alerts in the West Europe region.
  • Root Cause: The failure was due to an underlying dependency
  • Incident Timeline: 3 Hours & 7 minutes - 3/23, 23:25 UTC through 3/24, 2:32 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Eric Singleton

Update: Thursday, 24 March 2022 01:33 UTC

Root cause has been isolated to an underlying dependency which is in the process of recovering. Customers may experience up to 2 hours of ingestion latency and missed or delayed Log Search Alerts in the West Europe region
  • Work Around: None
  • Next Update: Before 03/24 04:00 UTC
-Eric Singleton

%3CLINGO-SUB%20id%3D%22lingo-sub-3265355%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20for%20Log%20Analytics%20-%2003%2F24%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3265355%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%20Thursday%2C%2024%20March%202022%2002%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%203%2F24%2C%2002%3A32%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%203%2F23%2C%2023%3A25%20UTC%20and%20that%20during%20the%203%20hours%20and%207%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20may%20experience%20up%20to%202%20hours%20of%20ingestion%20latency%20and%20missed%20or%20delayed%20Log%20Search%20Alerts%20in%20the%20West%20Europe%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20underlying%20dependency%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%207%20minutes%20-%203%2F23%2C%2023%3A25%20UTC%20through%203%2F24%2C%202%3A32%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%3EUpdate%3C%2FU%3E%3A%20Thursday%2C%2024%20March%202022%2001%3A33%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20an%20underlying%20dependency%20which%20is%20in%20the%20process%20of%20recovering.%20Customers%20may%20experience%20up%20to%202%20hours%20of%20ingestion%20latency%20and%20missed%20or%20delayed%20Log%20Search%20Alerts%20in%20the%20West%20Europe%20region%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%2F24%2004%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Eric%20Singleton%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:
‎Mar 23 2022 07:38 PM
Updated by: