%3CLINGO-SUB%20id%3D%22lingo-sub-1389877%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Metric%20Alerts%20-%2005%2F14%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1389877%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%20Thursday%2C%2014%20May%202020%2017%3A57%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2005%2F14%2C%2016%3A45%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2005%2F14%2C%2014%3A00%20UTC%20and%20that%20during%20the%202%20hours%20%26amp%3B%2045%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20the%20customers%20using%20Azure%20Monitor%20might%20have%20experienced%20failure%20notifications%20when%20performing%20service%20management%20operations%20such%20as%20create%2C%20update%2C%20delete%20for%20Azure%20Metric%20Alert%20Rules..%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20Based%20on%20our%20initial%20assessment%20the%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20back-end%20services%20.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20%26amp%3B%2045%20minutes%20-%2005%2F14%2C%2014%3A00%20UTC%20through%2005%2F14%2C%2016%3A45%20UTC%3C%2FLI%3E%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%3CUL%3E%0A%3C%2FUL%3E-Saika%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%20Thursday%2C%2014%20May%202020%2016%3A53%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20actively%20investigating%20an%20issue%20with%20Metric%20alerts.%20Some%20customers%20using%20Azure%20Monitor%20may%20experience%20failure%20notifications%20when%20performing%20service%20management%20operations%20such%20as%20create%2C%20update%2C%20delete%20for%20Azure%20Metric%20Alert%20Rules.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%3CNONE%20or%3D%22%22%20details%3D%22%22%3E%3C%2FNONE%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2005%2F14%2020%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E-Saika%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1389877%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 14 May 2020 17:57 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/14, 16:45 UTC. Our logs show the incident started on 05/14, 14:00 UTC and that during the 2 hours & 45 minutes that it took to resolve the issue some of the customers using Azure Monitor might have experienced failure notifications when performing service management operations such as create, update, delete for Azure Metric Alert Rules..
  • Root Cause: Based on our initial assessment the failure was due to an issue in one of our back-end services .
  • Incident Timeline: 2 Hours & 45 minutes - 05/14, 14:00 UTC through 05/14, 16:45 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.
-Saika

Initial Update: Thursday, 14 May 2020 16:53 UTC

We are actively investigating an issue with Metric alerts. Some customers using Azure Monitor may experience failure notifications when performing service management operations such as create, update, delete for Azure Metric Alert Rules.
  • Work Around:
  • Next Update: Before 05/14 20:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.

-Saika