Experiencing Data Latency for certain Data Types in Log Analytics - 02/17 - Resolved

Published Feb 16 2022 08:14 PM 634 Views
Final Update: Thursday, 17 February 2022 07:33 UTC

We've confirmed that all systems are back to normal with no customer impact as of 12/17, 06:35 UTC. Our logs show the incident started on 12/16, 16:16 UTC and that during the 14 hours and 20 minutes that it took to resolve the issue, some customers using Azure Log Analytics and Log Search Alerts in East US region may have experienced data latency for certain data types and missed alerts.
  • Root Cause: The failure was due to an issue in backend dependent service.
  • Incident Timeline: 14 Hours & 20 minutes - 12/16, 16:16 UTC through 12/17, 06:35 UTC
We understand that customers rely on Azure Log Analytics and Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Surya

Update: Thursday, 17 February 2022 04:08 UTC

Root cause has been isolated to configuration which was impacting logs ingestion. To address this issue we have redeployed service. Some customers may experience data latency for certain data types and missed alerts. and we estimate 4 hours before all backlog of data is addressed.
  • Work Around:
  • Next Update: Before 02/17 10:30 UTC
-chandar

%3CLINGO-SUB%20id%3D%22lingo-sub-3176700%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20for%20certain%20Data%20Types%20in%20Log%20Analytics%20-%2002%2F17%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3176700%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%2017%20February%202022%2007%3A33%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2012%2F17%2C%2006%3A35%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2012%2F16%2C%2016%3A16%20UTC%20and%20that%20during%20the%2014%20hours%20and%2020%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%20some%20customers%20using%20Azure%20Log%20Analytics%20and%20Log%20Search%20Alerts%20in%20East%20US%20region%20may%20have%20experienced%20data%20latency%20for%20certain%20data%20types%20and%20missed%20alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20backend%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2014%20Hours%20%26amp%3B%2020%20minutes%20-%2012%2F16%2C%2016%3A16%20UTC%20through%2012%2F17%2C%2006%3A35%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%20and%20Log%20Search%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Surya%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%2017%20February%202022%2004%3A08%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20configuration%20which%20was%20impacting%20logs%20ingestion.%20To%20address%20this%20issue%20we%20have%20redeployed%20service.%20Some%20customers%20may%20experience%20data%20latency%20for%20certain%20data%20types%20and%20missed%20alerts.%20and%20we%20estimate%204%20hours%20before%20all%20backlog%20of%20data%20is%20addressed.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%3CNONE%20or%3D%22%22%20details%3D%22%22%3E%3C%2FNONE%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2002%2F17%2010%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-chandar%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:
‎Feb 16 2022 11:36 PM
Updated by: