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

Published Jun 14 2021 04:52 AM 1,087 Views
Final Update: Monday, 14 June 2021 13:29 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/14, 13:15 UTC. Our logs show the incident started on 06/14 07:10 UTC and that during the 6 hours & 5 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 North Europe region.
  • Root Cause: The failure was due to an issue with our dependent service.
  • Incident Timeline: 6 Hours & 5 minutes - 06/14, 07:10 UTC through 06/14, 13:15 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Rahul

Initial Update: Monday, 14 June 2021 11:51 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers ingesting telemetry in North Europe region may experience intermittent data latency, data gaps and incorrect alert activation.
  • Work Around: None
  • Next Update: Before 06/14 16:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Rahul

%3CLINGO-SUB%20id%3D%22lingo-sub-2444384%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2006%2F14%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2444384%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%20Monday%2C%2014%20June%202021%2013%3A29%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%2F14%2C%2013%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F14%2007%3A10%20UTC%20and%20that%20during%20the%206%20hours%20%26amp%3B%205%20Minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%20some%20customers%20may%20have%20experienced%20issues%20ingesting%20telemetry%20in%20Log%20Analytics%20Workspace%20and%20may%20have%20experienced%26nbsp%3Bintermittent%20data%20latency%2C%20data%20gaps%20and%20incorrect%20alert%20activation%20in%20North%20Europe%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%206%20Hours%20%26amp%3B%205%20minutes%20-%2006%2F14%2C%2007%3A10%20UTC%20through%2006%2F14%2C%2013%3A15%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2014%20June%202021%2011%3A51%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20ingesting%20telemetry%20in%20North%20Europe%20region%20may%20experience%20intermittent%20data%20latency%2C%20data%20gaps%20and%20incorrect%20alert%20activation.%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%2006%2F14%2016%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Rahul%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:
‎Jun 14 2021 06:45 AM
Updated by: