%3CLINGO-SUB%20id%3D%22lingo-sub-2068398%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Metric%20Alerts%20-%2001%2F17%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2068398%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Sunday%2C%2017%20January%202021%2012%3A03%20UTC%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F17%2C%2011%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F17%2C%2010%3A00%20UTC%20and%20that%20during%20the%201%20hour%20that%20it%20took%20to%20resolve%20some%20of%20customers%20may%20experience%20missing%20of%20misfired%20alerts%20when%20using%20Azure%20Metric%20Alert%20Rules.%3C%2FSPAN%3E%3CBR%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%22%20helvetica%3D%22%22%20neue%3D%22%22%20%2F%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%20margin-bottom%3A%2012px%3B%20padding-left%3A%202.5em%3B%20list-style%3A%20outside%3B%20clear%3A%20left%3B%20color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20recent%20deployment%20task%20.%3CBR%20%2F%3E%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20-%2001%2F17%2C%2010%3A00%20UTC%20through%2001%2F17%2C%2011%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%20color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20SegoeUI%2C%20Lato%2C%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3EWe%20understand%20that%20customers%20rely%20on%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E-Soumyajeet%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2068398%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Sunday, 17 January 2021 12:03 UTC

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

-Soumyajeet