%3CLINGO-SUB%20id%3D%22lingo-sub-1066323%22%20slang%3D%22en-US%22%3EExperiencing%20failure%20in%20performing%20Metric%20Alert%20CRUD%20operations%20-%2012%2F14%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1066323%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%20Sunday%2C%2015%20December%202019%2018%3A36%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2012%2F15%2C%2018%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2012%2F14%2C%2006%3A00%20UTC%20and%20that%20during%20the%201%20day%2C%2012%20hours%20and%2015%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20could%20have%20experienced%20failure%20in%20performing%20Metric%20Alert%20CRUD%20operations%20on%20compute%20resources%20hosted%20in%20the%20East%20US%202%20region.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20dependent%20service.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20day%2C%2012%20Hours%20%26amp%3B%2015%20minutes%20-%2012%2F14%2C%2006%3A00%20UTC%20through%2012%2F15%2C%2018%3A15%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-Eric%20Singleton%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%3EUpdate%3C%2FU%3E%3A%20Saturday%2C%2014%20December%202019%2014%3A32%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Azure%20Monitor.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20may%20continue%20to%20experience%20failure%20in%20performing%20Metric%20Alert%20CRUD%20operation%20on%20compute%20resources%20hosted%20in%20EastUs2%20region.We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2012%2F14%20~06%3A00%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2012%2F15%2015%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Anusha%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Saturday%2C%2014%20December%202019%2009%3A59%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%3EWe%20are%20aware%20of%20issues%20within%20Metric%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20failure%20in%20performing%20Metric%20Alert%20CRUD%20operation%20on%20compute%20resources%20hosted%20in%20EastUs2%20region.%3C%2FDIV%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2012%2F14%2014%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Anusha%20Dodda%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1066323%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Sunday, 15 December 2019 18:36 UTC

We've confirmed that all systems are back to normal with no customer impact as of 12/15, 18:15 UTC. Our logs show the incident started on 12/14, 06:00 UTC and that during the 1 day, 12 hours and 15 minutes that it took to resolve the issue customers could have experienced failure in performing Metric Alert CRUD operations on compute resources hosted in the East US 2 region.
  • Root Cause: The failure was due to a dependent service.
  • Incident Timeline: 1 day, 12 Hours & 15 minutes - 12/14, 06:00 UTC through 12/15, 18:15 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Eric Singleton

Update: Saturday, 14 December 2019 14:32 UTC

We continue to investigate issues within Azure Monitor. Root cause is not fully understood at this time. Some customers may continue to experience failure in performing Metric Alert CRUD operation on compute resources hosted in EastUs2 region.We are working to establish the start time for the issue, initial findings indicate that the problem began at 12/14 ~06:00 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 12/15 15:00 UTC
-Anusha

Initial Update: Saturday, 14 December 2019 09:59 UTC

We are aware of issues within Metric Alerts and are actively investigating. Some customers may experience failure in performing Metric Alert CRUD operation on compute resources hosted in EastUs2 region.
  • Work Around: None
  • Next Update: Before 12/14 14:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anusha Dodda