Home
%3CLINGO-SUB%20id%3D%22lingo-sub-823313%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2008%2F26%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-823313%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%3CDIV%20style%3D%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EFinal%20Update%3C%2FU%3E%3A%20Monday%2C%2026%20August%202019%2021%3A41%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%20style%3D%22%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2008%2F26%2C%2020%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F26%2C%2017%3A50%20UTC%20and%20that%20during%20the%202%20hours%2010%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20~8%25%20of%20the%20customers%20using%20Log%20alerts%20which%20are%20configured%20in%20East%20US%20region%20might%20have%20experienced%20Alerting%20failure.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%26nbsp%3B%20%26nbsp%3BRoot%20Cause%3A%20The%20failure%20was%20due%20to%20issues%20in%20one%20of%20our%20back-end%20services.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%26nbsp%3B%20%26nbsp%3BIncident%20Timeline%3A%202%20Hours%20%26amp%3B%2010%20minutes%20-%2008%2F26%2C%2017%3A50%20UTC%20through%2008%2F26%2C%2020%3A00%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3EWe%20understand%20that%20customers%20rely%20on%20Log%20Search%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E-Venkat%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%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%3CDIV%20style%3D%22font-size%3A14px%3B%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%20Monday%2C%2026%20August%202019%2018%3A52%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%26nbsp%3B%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3Ealerting%20failures%20in%20East%20US%20region%3C%2FSPAN%3E.%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%2008%2F26%2022%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-venkat%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-823313%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 26 August 2019 21:41 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/26, 20:00 UTC. Our logs show the incident started on 08/26, 17:50 UTC and that during the 2 hours 10 minutes that it took to resolve the issue ~8% of the customers using Log alerts which are configured in East US region might have experienced Alerting failure.

   Root Cause: The failure was due to issues in one of our back-end services.
   Incident Timeline: 2 Hours & 10 minutes - 08/26, 17:50 UTC through 08/26, 20:00 UTC

We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Venkat


Initial Update: Monday, 26 August 2019 18:52 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience alerting failures in East US region.
  • Work Around: none
  • Next Update: Before 08/26 22:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-venkat