Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1085363%22%20slang%3D%22en-US%22%3EExperiencing%20Query%20and%20Alerting%20failure%20issues%20for%20Azure%20Monitor%20in%20West%20Europe%20-%2001%2F02%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1085363%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%3EFinal%20Update%3C%2FU%3E%3A%20Thursday%2C%2002%20January%202020%2007%3A02%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F02%2C%2006%3A45%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F02%2C%2006%3A05%20UTC%20and%20that%20during%20the%2040%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20West%20Europe%20region%20might%20have%20experienced%20Alerting%20failures%20or%20delayed%20alerts%20issue.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2040%20minutes%20-%2001%2F02%2C%2006%3A05%20UTC%20through%2001%2F02%2C%2006%3A45%20UTC%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-Madhuri%3CBR%20%2F%3E%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-1085363%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 02 January 2020 07:02 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/02, 06:45 UTC. Our logs show the incident started on 01/02, 06:05 UTC and that during the 40 minutes that it took to resolve the issue some customers in West Europe region might have experienced Alerting failures or delayed alerts issue.
  • Root Cause: The failure was due to an issue in one of our dependent services.
  • Incident Timeline: 40 minutes - 01/02, 06:05 UTC through 01/02, 06:45 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Madhuri