%3CLINGO-SUB%20id%3D%22lingo-sub-1121859%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2001%2F22%20-%20Investigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1121859%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%3EInitial%20Update%3C%2FU%3E%3A%20Wednesday%2C%2022%20January%202020%2009%3A12%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Search%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20have%20experience%20facing%20failure%20in%20receiving%20alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F22%2013%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Satya%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-1121859%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 22 January 2020 10:17 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/22, 09:20 UTC. Our logs show the incident started on 01/22, 08:10 UTC and that during the 1 hour and 10 minutes that it took to resolve the issue all customers in West Europe region may have experienced alerting delays and missed alerts for Log Search Alerts.

  • Root Cause: The failure was due to an issue with the deployment in one of the backend service. 
  • Incident Timeline: 1 Hour & 10 minutes - 01/22, 08:10 UTC through 01/22, 09:20 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Satya

Initial Update: Wednesday, 22 January 2020 09:12 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers may have experience facing failure in receiving alerts.
  • Work Around: None
  • Next Update: Before 01/22 13:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Satya