Experiencing Alerting Latency for Activity Log Alerts - 09/01 - Resolved

Published Sep 01 2021 01:06 PM 678 Views
Final Update: Wednesday, 01 September 2021 21:01 UTC

We've confirmed that all systems are back to normal with no customer impact as of 9/1, 20:15 UTC. Our logs show the incident started on 9/1, 15:00 UTC and that during the five hours that it took to resolve the issue approximately 450 total customers may have experienced delayed activity log alerts.
  • Root Cause: The failure was due to a Backend service responsible for processing activity logs hitting an operational threshold, which caused a delay in the processing of activity logs.
  • Incident Timeline: 5 Hours & 15 minutes - 9/1, 15:00 UTC through 9/1, 20:15 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused.

-Jack Cantwell

Initial Update: Wednesday, 01 September 2021 20:05 UTC

We are aware of issues within Activity Log Alerts and are actively investigating. Some customers may experience delayed or missed Log Search Alerts.
  • Next Update: Before 09/01 21:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jack Cantwell

%3CLINGO-SUB%20id%3D%22lingo-sub-2709072%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20Latency%20for%20Activity%20Log%20Alerts%20-%2009%2F01%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2709072%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%2001%20September%202021%2021%3A01%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%2F1%2C%2020%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%209%2F1%2C%2015%3A00%20UTC%20and%20that%20during%20the%20five%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20approximately%20450%20total%20customers%20may%20have%20experienced%20delayed%20activity%20log%20alerts.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%26nbsp%3B%3CSPAN%20style%3D%22font-size%3A11.0pt%3Bfont-family%3A%26quot%3BCalibri%26quot%3B%2Csans-serif%3B%0Amso-fareast-font-family%3ACalibri%3Bmso-fareast-theme-font%3Aminor-latin%3Bmso-ansi-language%3A%0AEN-US%3Bmso-fareast-language%3AEN-US%3Bmso-bidi-language%3AAR-SA%22%3EBackend%20service%20responsible%20for%20processing%20activity%20logs%20hitting%20an%20operational%20threshold%2C%20which%20caused%20a%20delay%20in%20the%20processing%20of%20activity%20logs%3C%2FSPAN%3E.%3C%2FLI%3E%0A%20%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%205%20Hours%20%26amp%3B%2015%20minutes%20-%209%2F1%2C%2015%3A00%20UTC%20through%209%2F1%2C%2020%3A15%20UTC%3CBR%20%2F%3E%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-Jack%20Cantwell%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%2001%20September%202021%2020%3A05%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Activity%20Log%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20delayed%20or%20missed%20Log%20Search%20Alerts.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2009%2F01%2021%3A30%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
Version history
Last update:
‎Sep 01 2021 02:04 PM
Updated by: