%3CLINGO-SUB%20id%3D%22lingo-sub-1858793%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Gaps%20in%20Azure%20portal%20for%20Log%20Analytics%20in%20East%20US%202%20-%2011%2F05%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1858793%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%20Thursday%2C%2005%20November%202020%2020%3A51%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2011%2F5%2C%2020%3A22%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2011%2F5%2C%2019%3A45%20UTC%20and%20that%20during%20the%2037%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20166%20customers%20experienced%20latent%20log%20ingestion%20and%20possible%20data%20gaps.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20backend%20cache%20being%20pushed%20past%20an%20operational%20threshold.%20The%20system%20was%20scaled%20out%20to%20mitigate%20the%20issue.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2037%20minutes%20-%2011%2F5%2C%2019%3A45%20UTC%20through%2011%2F5%2C%2020%3A22%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-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%3EInitial%20Update%3C%2FU%3E%3A%20Thursday%2C%2005%20November%202020%2020%3A13%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20in%20East%20US%202%20region%20may%20be%20experiencing%20intermittent%20data%20gaps.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2011%2F05%2022%3A30%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%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%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1858793%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 05 November 2020 20:51 UTC

We've confirmed that all systems are back to normal with no customer impact as of 11/5, 20:22 UTC. Our logs show the incident started on 11/5, 19:45 UTC and that during the 37 minutes that it took to resolve the issue 166 customers experienced latent log ingestion and possible data gaps.
  • Root Cause: The failure was due to backend cache being pushed past an operational threshold. The system was scaled out to mitigate the issue.
  • Incident Timeline: 37 minutes - 11/5, 19:45 UTC through 11/5, 20:22 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jeff

Initial Update: Thursday, 05 November 2020 20:13 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers in East US 2 region may be experiencing intermittent data gaps.
  • Next Update: Before 11/05 22:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jeff