Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1007010%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20in%20West%20US%202-%2011%2F13%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1007010%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%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Wednesday%2C%2013%20November%202019%2022%3A06%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2011%2F13%2C%2021%3A25%26nbsp%3BUTC.%20Our%20logs%20show%20the%20incident%20started%20on%2011%2F13%2C%2020%3A25%20UTC%20and%20that%20during%20the%201%20hour%20that%20it%20took%20to%20resolve%20the%20issue%20subset%20of%20Log%20Analytics%20customers%20in%20West%20US%202%20might%20have%20experienced%20failures%20in%20Log%20Search%20Alerts.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20in%20one%20of%20the%20dependent%20services.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20-%2011%2F13%2C%2020%3A25%26nbsp%3BUTC%26nbsp%3BUTC%20through%2011%2F13%2C%2021%3A25%26nbsp%3BUTC%3CBR%20%2F%3E%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-Venkat%3CBR%20%2F%3E%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-1007010%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 13 November 2019 22:06 UTC

We've confirmed that all systems are back to normal with no customer impact as of 11/13, 21:25 UTC. Our logs show the incident started on 11/13, 20:25 UTC and that during the 1 hour that it took to resolve the issue subset of Log Analytics customers in West US 2 might have experienced failures in Log Search Alerts.

  • Root Cause: The failure was due to issue in one of the dependent services.
  • Incident Timeline: 1 Hour - 11/13, 20:25 UTC UTC through 11/13, 21:25 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Venkat