Home
%3CLINGO-SUB%20id%3D%22lingo-sub-498660%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2004%2F29%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-498660%22%20slang%3D%22en-US%22%3EFinal%20Update%3A%20Monday%2C%2029%20April%202019%2011%3A03%20UTCWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2004%2F29%2C%2010%3A45%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2004%2F29%2C%2008%3A20%20UTC%20and%20that%20during%20the%202%20hours%2025%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%20Customers%20must%20have%20experienced%20Alerting%20failures%20for%20the%20alerts%20configured%20in%20the%20Australia%20-%20South%20East%20Region.%3CBR%20%2F%3E%20Root%20Cause%3A%20The%20failure%20was%20due%20to%20the%20issues%20in%20one%20of%20our%20dependent%20services.%26nbsp%3B%20Incident%20Timeline%3A%26nbsp%3B%202%20hours%2025%20minutes%20-%26nbsp%3B%2004%2F29%2C%2004%2F29%2C%2008%3A20%20UTC%20through%2004%2F29%2C%2010%3A45%20UTCWe%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-Monish%3CBR%20%2F%3E%20Initial%20Update%3A%20Monday%2C%2029%20April%202019%2010%3A34%20UTCWe%20are%20aware%20of%20issues%20within%20Log%20Search%20Alerts%20and%20are%20actively%20investigating.%20Customers%20may%20experience%20Alerting%20failures%20for%20the%20Alerts%20configured%20in%20the%20Australia%20-%20South%20East%20Region.%3CBR%20%2F%3E%20Work%20Around%3A%20None%20Next%20Update%3A%20Before%2004%2F29%2014%3A00%20UTCWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Monish%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-498660%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 29 April 2019 11:03 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/29, 10:45 UTC. Our logs show the incident started on 04/29, 08:20 UTC and that during the 2 hours 25 minutes that it took to resolve the issue, Customers must have experienced Alerting failures for the alerts configured in the Australia - South East Region.
  • Root Cause: The failure was due to the issues in one of our dependent services. 
  • Incident Timeline2 hours 25 minutes 04/29, 04/29, 08:20 UTC through 04/29, 10:45 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Monish

Initial Update: Monday, 29 April 2019 10:34 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Customers may experience Alerting failures for the Alerts configured in the Australia - South East Region.
  • Work Around: None
  • Next Update: Before 04/29 14:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Monish