Experiencing Data Latency issue in Log Analytics in East US region - 12/30 - Resolved

Published Dec 29 2019 08:27 PM 1,261 Views
Final Update: Monday, 30 December 2019 04:10 UTC

We've confirmed that all systems are back to normal with no customer impact as of 12/30, 04:04 UTC. Our logs show the incident started on 12/30, 00:28 UTC and that during the 3 hours and 36 minutes that it took to resolve the issue customers in East US region might have experienced Alerting failure or Delayed alerts .
  • Root Cause: The failure was due to an issue in one of the dependent services.
  • Incident Timeline: 3 Hours & 36 minutes - 12/30, 00:28 UTC through 12/30, 04:04 UTC
We understand that customers rely on Log Analytics as a critical service and apologize for any impact this incident caused.

-Madhuri

%3CLINGO-SUB%20id%3D%22lingo-sub-1082921%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20issue%20in%20Log%20Analytics%20in%20East%20US%20region%20-%2012%2F30%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1082921%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%20Monday%2C%2030%20December%202019%2004%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%2012%2F30%2C%2004%3A04%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2012%2F30%2C%2000%3A28%20UTC%20and%20that%20during%20the%203%20hours%20and%2036%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20in%20East%20US%20region%20might%20have%20experienced%20Alerting%20failure%20or%20Delayed%20alerts%26nbsp%3B.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20the%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2036%20minutes%20-%2012%2F30%2C%2000%3A28%20UTC%20through%2012%2F30%2C%2004%3A04%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Log%20Analytics%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Madhuri%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%3CLINGO-LABS%20id%3D%22lingo-labs-1082921%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Dec 29 2019 08:27 PM
Updated by: