%3CLINGO-SUB%20id%3D%22lingo-sub-1269982%22%20slang%3D%22en-US%22%3EExperiencing%20failure%20or%20delay%20in%20Alerts%20for%20Metric%20Alerts%20-%2004%2F01%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1269982%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%20Wednesday%2C%2001%20April%202020%2003%3A11%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2004%2F01%2C%2002%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F31%2C%2023%3A00%20UTC%20and%20that%20during%20the%203%20hours%20and%2030%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20using%20Azure%20metric%20alerts%20may%20not%20have%20received%20or%20experienced%20delays%20in%20receiving%20some%20metric%20alerts%20and%20additionally%20some%20alerts%20would%20have%20misfired.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20with%20one%20of%20the%20backend%20services.%20%26nbsp%3B%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20Hours%20%26amp%3B%2030%20minutes%20-%2003%2F31%2C%2023%3A00%20UTC%20through%2004%2F01%2C%2002%3A30%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Metric%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Jayadev%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-1269982%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 01 April 2020 03:11 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/01, 02:30 UTC. Our logs show the incident started on 03/31, 23:00 UTC and that during the 3 hours and 30 minutes that it took to resolve the issue some customers using Azure metric alerts may not have received or experienced delays in receiving some metric alerts and additionally some alerts would have misfired.
  • Root Cause: The failure was due to issues with one of the backend services.  
  • Incident Timeline: 3 Hours & 30 minutes - 03/31, 23:00 UTC through 04/01, 02:30 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Jayadev