Home
%3CLINGO-SUB%20id%3D%22lingo-sub-873014%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Ingest%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2009%2F24%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-873014%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%2024%20September%202019%2022%3A30%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%209%2F24%2C%2022%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%209%2F24%2C%209%3A00%20UTC%20and%20that%20during%20the%2013.5%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20experienced%20up%20to%204%20hours%20of%20ingestion%20delay%20in%20East%20US%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20backend%20service%20scaling%20issue%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-Jeff%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%20Tuesday%2C%2024%20September%202019%2021%3A10%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EMitigation%20is%20still%20in%20progress%2C%20engineers%20are%20continuing%20to%20see%20improvement%20in%20ingestion%20times%20in%20East%20US%20region%20but%20have%20no%20fully%20resolved%20the%20issue.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E-Jeff%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EUpdate%3C%2FU%3E%3A%20Tuesday%2C%2024%20September%202019%2017%3A39%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ELog%20Analytics%20ingestion%20in%20East%20US%20region%20has%20a%20recent%20ingestion%20latency%20issue%20with%20a%20maximum%20ingestion%20latency%20of%204%20hours.%20Root%20cause%20has%20been%20isolated%20to%20a%20service%20scale%20issue%20which%20was%20impacting%20Log%20Analytics%20ingestion.%20As%20a%20result%20of%20this%20ingestion%20latency%20customers%20may%20experience%20alerts%20not%20behaving%20in%20the%20expected%20manner%20due%20to%20missing%20data.%20To%20address%20this%20issue%20we%20have%20scaled%20the%20service%20appropriately.%20Some%20customers%20will%20experience%20incomplete%20or%20delayed%20ingestion%20until%20full%20mitigation%20which%20we%20estimate%20to%20be%20in%20approximately%203%20hours.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2009%2F24%2020%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Jeff%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%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-873014%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EService%20Map%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 24 September 2019 22:30 UTC

We've confirmed that all systems are back to normal with no customer impact as of 9/24, 22:30 UTC. Our logs show the incident started on 9/24, 9:00 UTC and that during the 13.5 hours that it took to resolve the issue customers experienced up to 4 hours of ingestion delay in East US region.
  • Root Cause: The failure was due to a backend service scaling issue
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jeff

Update: Tuesday, 24 September 2019 21:10 UTC

Mitigation is still in progress, engineers are continuing to see improvement in ingestion times in East US region but have no fully resolved the issue.

-Jeff

Update: Tuesday, 24 September 2019 17:39 UTC

Log Analytics ingestion in East US region has a recent ingestion latency issue with a maximum ingestion latency of 4 hours. Root cause has been isolated to a service scale issue which was impacting Log Analytics ingestion. As a result of this ingestion latency customers may experience alerts not behaving in the expected manner due to missing data. To address this issue we have scaled the service appropriately. Some customers will experience incomplete or delayed ingestion until full mitigation which we estimate to be in approximately 3 hours.
  • Next Update: Before 09/24 20:00 UTC
-Jeff