%3CLINGO-SUB%20id%3D%22lingo-sub-1517672%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2007%2F13%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1517672%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%2013%20July%202020%2001%3A08%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2007%2F13%2C%2000%3A55%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2007%2F12%2C%2020%3A50%20UTC%20and%20that%20during%20the%20~4%26nbsp%3B%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20in%20West%20US%20experienced%20failed%20or%20misfired%20alerts.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20unhealthy%20backend%20service.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%204%20Hours%20%26amp%3B%205%20minutes%20-%2007%2F12%2C%2020%3A50%20UTC%26nbsp%3Bthrough%2007%2F13%2C%2000%3A55%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Log%20Search%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Anupama%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%20Monday%2C%2013%20July%202020%2000%3A08%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Search%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20delayed%20or%20misfired%20alerts%20in%20West%20US%20region.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2007%2F13%2003%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E%3CBR%20%2F%3E-Sindhu%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-1517672%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 13 July 2020 01:08 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/13, 00:55 UTC. Our logs show the incident started on 07/12, 20:50 UTC and that during the ~4  hours that it took to resolve the issue customers in West US experienced failed or misfired alerts.
  • Root Cause: The failure was due to unhealthy backend service.
  • Incident Timeline: 4 Hours & 5 minutes - 07/12, 20:50 UTC through 07/13, 00:55 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Anupama

Initial Update: Monday, 13 July 2020 00:08 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience delayed or misfired alerts in West US region.
  • Next Update: Before 07/13 03:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Sindhu