%3CLINGO-SUB%20id%3D%22lingo-sub-1291269%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Metric%20Alerts%20Rules%20-%2004%2F08%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1291269%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%2008%20April%202020%2009%3A44%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%2F08%2C%2008%3A25%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2004%2F08%2C%2007%3A05%20UTC%20and%20that%20during%20the%201%20hour%20%26amp%3B%2020%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20experienced%20%3CSPAN%20style%3D%22font-size%3A10.5pt%3Bline-height%3A107%25%3B%0Afont-family%3A%26quot%3BHelvetica%26quot%3B%2Csans-serif%3Bmso-fareast-font-family%3A%26quot%3BTimes%20New%20Roman%26quot%3B%3B%0Amso-bidi-font-family%3A%26quot%3BTimes%20New%20Roman%26quot%3B%3Bcolor%3Ablack%3Bbackground%3Awhite%3Bmso-ansi-language%3A%0AEN-US%3Bmso-fareast-language%3AEN-US%3Bmso-bidi-language%3AAR-SA%22%3Efailures%20in%20creating%20or%20updating%20azure%20metric%20alerts%20rules%20in%20West%20central%20US%2C%20East%20Asia%2C%20North%20Europe%2C%20South%20central%20US%2C%20West%20Europe%20and%20East%20US%20regions%3C%2FSPAN%3E%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20transient%20error%20in%20one%20of%20the%20back%20end%20service%20and%20auto%20mitigated%3CSPAN%20style%3D%22font-size%3A10.5pt%3Bline-height%3A107%25%3Bfont-family%3A%26quot%3B%26amp%3Bquot%26quot%3B%2Cserif%3B%0Amso-fareast-font-family%3A%26quot%3BTimes%20New%20Roman%26quot%3B%3Bmso-bidi-font-family%3A%26quot%3BTimes%20New%20Roman%26quot%3B%3B%0Acolor%3Ablack%3Bmso-ansi-language%3AEN-US%3Bmso-fareast-language%3AEN-US%3Bmso-bidi-language%3A%0AAR-SA%22%3E.%20%3C%2FSPAN%3E%26nbsp%3B%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2020%20minutes%20-%2004%2F08%2C%2007%3A05%20UTC%20through%2004%2F08%2C%2008%3A25%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-Satya%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%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-1291269%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 08 April 2020 09:44 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/08, 08:25 UTC. Our logs show the incident started on 04/08, 07:05 UTC and that during the 1 hour & 20 minutes that it took to resolve the issue some of customers experienced failures in creating or updating azure metric alerts rules in West central US, East Asia, North Europe, South central US, West Europe and East US regions
  • Root Cause: The failure was due to transient error in one of the back end service and auto mitigated.  
  • Incident Timeline: 1 Hour & 20 minutes - 04/08, 07:05 UTC through 04/08, 08:25 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Satya