Home
%3CLINGO-SUB%20id%3D%22lingo-sub-812555%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2008%2F20%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-812555%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%20Tuesday%2C%2020%20August%202019%2013%3A04%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2008%2F20%2C%2012%3A12%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F20%2C%2009%3A15%20UTC%20and%20that%20during%20the%202%20hours%2057%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20~19%25%20customers%20using%20Log%20alerts%20which%20are%20configured%20in%20West%20Europe%20region%20might%20have%20experienced%20Alerting%20failure%20issues.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20in%20one%20of%20our%20backend%20services.%26nbsp%3B%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%2057%20minutes%20-%208%2F20%2C%2009%3A15%20UTC%20through%208%2F20%2C%2012%3A12%20UTC%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-Anmol%3CBR%20%2F%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%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Tuesday%2C%2020%20August%202019%2011%3A29%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Search%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20in%20the%20West%20Europe%20region%20may%20experience%20intermittent%20alerting%20failures.%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%2F20%2013%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Anmol%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-812555%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-813213%22%20slang%3D%22en-US%22%3ERe%3A%20Experiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2008%2F20%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-813213%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20unable%20to%20connect%20to%20live%20metrics%20stream%20in%20Azure%20Government.%20Message%20displayed%20is%20%22Data%20is%20temporarily%20inaccessible.%20%26nbsp%3B%3CSPAN%3EThe%20updates%20on%20our%20status%20are%20posted%20here%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Faistatus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Faistatus%3C%2FA%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Final Update: Tuesday, 20 August 2019 13:04 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/20, 12:12 UTC. Our logs show the incident started on 08/20, 09:15 UTC and that during the 2 hours 57 minutes that it took to resolve the issue ~19% customers using Log alerts which are configured in West Europe region might have experienced Alerting failure issues.
  • Root Cause: The failure was due to issues in one of our backend services. 
  • Incident Timeline: 2 Hours 57 minutes - 8/20, 09:15 UTC through 8/20, 12:12 UTC
We understand that customers rely on Log Search Alerts as a critical service and apologize for any impact this incident caused.

-Anmol

Initial Update: Tuesday, 20 August 2019 11:29 UTC

We are aware of issues within Log Search Alerts and are actively investigating. Some customers in the West Europe region may experience intermittent alerting failures.
  • Work Around: None
  • Next Update: Before 08/20 13:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anmol

1 Comment
Occasional Visitor

We are unable to connect to live metrics stream in Azure Government. Message displayed is "Data is temporarily inaccessible.  The updates on our status are posted here http://aka.ms/aistatus"