Experiencing Data Latency Issue in Azure portal for Log Analytics - 06/17 - Resolved

Published Jun 17 2021 08:46 AM 660 Views
Final Update: Thursday, 17 June 2021 15:43 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/17, 14:10 UTC. Our logs show the incident started on 06/17, 11:55 UTC and that during the 2 hours & 15 minutes that it took to resolve the issue, some customers may have experienced issues ingesting telemetry in Log Analytics Workspace and may have experienced intermittent data latency, data gaps and incorrect alert activation in UK South region.
  • Root Cause: The failure was due to an issue with our dependent service.
  • Incident Timeline: 2 Hours & 15 minutes - 06/17, 11:55 UTC through 06/17, 14:10 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Rahul

%3CLINGO-SUB%20id%3D%22lingo-sub-2458728%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2006%2F17%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2458728%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%20June%202021%2015%3A43%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2006%2F17%2C%2014%3A10%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F17%2C%2011%3A55%20UTC%20and%20that%20during%20the%202%20hours%20%26amp%3B%2015%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%26nbsp%3Bsome%20customers%20may%20have%20experienced%20issues%20ingesting%20telemetry%20in%20Log%20Analytics%20Workspace%20and%20may%20have%20experienced%20intermittent%20data%20latency%2C%20data%20gaps%20and%20incorrect%20alert%20activation%20in%20UK%20South%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20with%20our%20dependent%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20%26amp%3B%2015%20minutes%20-%2006%2F17%2C%2011%3A55%20UTC%20through%2006%2F17%2C%2014%3A10%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-Rahul%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jun 17 2021 08:46 AM
Updated by: