Experiencing Data Access Issue in Azure portal for Log Analytics - 05/18 - Resolved

Published May 18 2021 01:36 PM 735 Views
Final Update: Tuesday, 18 May 2021 20:15 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/18, 16:00 UTC. Our logs show the incident started on 05/18, 12:00 UTC and that during the 4 hours that it took to resolve the issue customers using Log Analytics in UK South  may have experienced intermittent data latency and incorrect alert activation for resources in this region.
  • Root Cause: After our investigation, we found that a backend scale unit become unhealthy due to an ingestion error. This ingestion is to process logging data for Log Analytics and caused alert systems to fail.
  • Incident Timeline: 4 Hours  - 05/18, 12:00  UTC through 05/18, 16:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Vincent

%3CLINGO-SUB%20id%3D%22lingo-sub-2366082%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2005%2F18%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2366082%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%20Tuesday%2C%2018%20May%202021%2020%3A15%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2005%2F18%2C%2016%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2005%2F18%2C%2012%3A00%20UTC%20and%20that%20during%20the%204%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20using%20Log%20Analytics%20in%20UK%20South%26nbsp%3B%20may%20have%20experienced%20intermittent%20data%20latency%20and%20incorrect%20alert%20activation%20for%20resources%20in%20this%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20After%20our%20investigation%2C%20we%20found%20that%20a%20backend%20scale%20unit%20become%20unhealthy%20due%20to%20an%20ingestion%20error.%20This%20ingestion%20is%20to%20process%20logging%20data%20for%20Log%20Analytics%20and%20caused%20alert%20systems%20to%20fail.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%204%20Hours%26nbsp%3B%20-%2005%2F18%2C%2012%3A00%26nbsp%3B%20UTC%20through%2005%2F18%2C%2016%3A00%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-Vincent%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:
‎May 18 2021 01:36 PM
Updated by: