Experiencing ingestion latency Issue in Azure portal for Log Analytics - 03/10 - Resolved

Published 03-10-2021 10:36 AM 828 Views
Final Update: Wednesday, 10 March 2021 19:10 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/10, 18:45 UTC. Our logs show that the incident started on 03/10, 17:20 UTC and that during the 1 hour and 25 minutes that it took to resolve the issue some of the customers experienced delayed log ingestion if their Workspaces is in the West Europe region.
  • Root Cause: The failure was due to an issue in one of our backend services.
  • Incident Timeline: 1 Hours & 25 minutes - 03/10, 17:20 UTC through 03/10, 18:45 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Saika

Initial Update: Wednesday, 10 March 2021 18:34 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delayed log ingestion if their workspace is in the West Europe region.
  • Work Around: none
  • Next Update: Before 03/10 20:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jack Cantwell

%3CLINGO-SUB%20id%3D%22lingo-sub-2200223%22%20slang%3D%22en-US%22%3EExperiencing%20ingestion%20latency%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2003%2F10%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2200223%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%20Wednesday%2C%2010%20March%202021%2019%3A10%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2003%2F10%2C%2018%3A45%20UTC.%20Our%20logs%20show%20that%20the%20incident%20started%20on%2003%2F10%2C%2017%3A20%20UTC%20and%20that%20during%20the%201%20hour%20and%2025%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20the%20customers%20experienced%20delayed%20log%20ingestion%20if%20their%20Workspaces%20is%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%20issue%20in%20one%20of%20our%20backend%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%2025%20minutes%20-%2003%2F10%2C%2017%3A20%20UTC%20through%2003%2F10%2C%2018%3A45%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-Saika%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%20Wednesday%2C%2010%20March%202021%2018%3A34%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20delayed%20log%20ingestion%20if%20their%20workspace%20is%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%2F10%2020%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jack%20Cantwell%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2200223%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Mar 10 2021 11:15 AM
Updated by: