Final Update: Tuesday, 09 July 2019 11:38 UTC
We've confirmed that all systems are back to normal with no customer impact as of 07/09, 09:50 UTC. Our logs show the incident started on 07/09, 08:20 UTC and that during the 1 hours 30 minutes that it took to resolve the issue customers would have experienced failure while performing CRUD operations on log search alerts. Existing log search alerts would have worked as expected.
-
Root Cause: The failure was due to dependent service which went into unhealthy state.
-
Incident Timeline: 1 Hours & 30 minutes - 07/09, 08:20 UTC through 07/09, 09:50 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.
-Rama
