%3CLINGO-SUB%20id%3D%22lingo-sub-1592744%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Activity%20Log%20Alerts%20-%2008%2F17%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1592744%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%2017%20August%202020%2011%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%2008%2F17%2C%2011%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F17%2C%2007%3A50%20UTC%20and%20that%20during%20the%203%20hours%20and%2025%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20using%20Activity%20Log%20Alerts%20in%20Azure%20China%20experienced%20issues%20with%20delayed%20alerts%20up%20to%202%20hours%20and%2050%20minutes.%20Alerts%20would%20have%20eventually%20fired.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20with%20one%20of%20the%20backend%20services.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2025%20minutes%20-%2008%2F17%2C%2007%3A50%20UTC%20through%2008%2F17%2C%2011%3A15%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Activity%20Log%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Jayadev%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-1592744%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 17 August 2020 11:51 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/17, 11:15 UTC. Our logs show the incident started on 08/17, 07:50 UTC and that during the 3 hours and 25 minutes that it took to resolve the issue customers using Activity Log Alerts in Azure China experienced issues with delayed alerts up to 2 hours and 50 minutes. Alerts would have eventually fired.
  • Root Cause: The failure was due to issues with one of the backend services.
  • Incident Timeline: 3 Hours & 25 minutes - 08/17, 07:50 UTC through 08/17, 11:15 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused.

-Jayadev