%3CLINGO-SUB%20id%3D%22lingo-sub-2070494%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Metric%20Alerts%20-%2001%2F18%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2070494%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%20Monday%2C%2018%20January%202021%2011%3A30%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%2F18%2C%2011%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F18%2C%2010%3A00%20UTC%20and%20that%20during%20the%201%20hour%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20missing%20or%20misfired%20alerts%20in%20East%20US%20region%20while%20using%20Azure%20Metric%20Alert%20Rules.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%26nbsp%3Ba%20recent%20deployment%20task%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201Hour%20%26amp%3B%200%20minutes%20-%2001%2F18%2C%2010%3A00%20UTC%20through%2001%2F18%2C%2011%3A00%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-Deepika%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-2070494%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 18 January 2021 11:30 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/18, 11:00 UTC. Our logs show the incident started on 01/18, 10:00 UTC and that during the 1 hour that it took to resolve the issue some customers may have experienced missing or misfired alerts in East US region while using Azure Metric Alert Rules.
  • Root Cause: The failure was due to a recent deployment task
  • Incident Timeline: 1Hour & 0 minutes - 01/18, 10:00 UTC through 01/18, 11:00 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Deepika