%3CLINGO-SUB%20id%3D%22lingo-sub-1346343%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2004%2F29%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1346343%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%2029%20April%202020%2011%3A39%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%2F29%2C%2011%3A20%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2004%2F22%2C%2017%3A00%20UTC%20and%20that%20during%20the%206%20days%2018%20hours%20and%2020%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20missed%20alerts%20on%20SQL%20resources%20for%20alert%20rules%20that%20were%20created%20before%2004%2F23%2012%3A00%20UTC%20in%20Public%20cloud%2C%20US%20Gov%20cloud%2C%20China%20Gov%20cloud.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20with%20configuration%20changes%20in%20one%20of%20our%20back%20end%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%206%20Days%2018%20Hours%20%26amp%3B%2020%20minutes%20-%2004%2F22%2C%2017%3A00%20UTC%20through%2004%2F29%2C%2011%3A20%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E-Syed%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%20Wednesday%2C%2029%20April%202020%2010%3A27%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Azure%20Metric%20Alerts.%20Some%20customers%20continue%20to%20experience%20missing%20alerts%20on%20SQL%20resources%20for%20alert%20rules%20that%20were%20created%20before%2004%2F23%2012%3A00%20UTC%20in%20Public%20cloud%2C%20US%20Gov%20cloud%2C%20China%20Gov%20cloud.%20Initial%20findings%20indicate%20that%20the%20problem%20began%20at%2004%2F22%20~17.00%20UTC.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%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%2004%2F29%2014%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Syed%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%20Wednesday%2C%2029%20April%202020%2005%3A48%20UTC%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CDIV%20style%3D%22%22%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3CDIV%20style%3D%22%22%3EWe%20continue%20to%20investigate%20issues%20within%20Azure%20Metric%20Alerts.%20Some%20customers%20continue%20to%20experience%20missing%20alerts%20on%20SQL%20resources%20for%20alert%20rules%20that%20were%20created%20before%2004%2F23%2012%3A00%20UTC%20in%20Public%20cloud%2C%20US%20Gov%20cloud%2C%20China%20Gov%20cloud.%20Initial%20findings%20indicate%20that%20the%20problem%20began%20at%2004%2F22%20~17.00%20UTC.%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%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%2004%2F29%2010%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Syed%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1346343%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 29 April 2020 11:39 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/29, 11:20 UTC. Our logs show the incident started on 04/22, 17:00 UTC and that during the 6 days 18 hours and 20 minutes that it took to resolve the issue some customers may have missed alerts on SQL resources for alert rules that were created before 04/23 12:00 UTC in Public cloud, US Gov cloud, China Gov cloud.

  • Root Cause: The failure was due to an issue with configuration changes in one of our back end service.
  • Incident Timeline: 6 Days 18 Hours & 20 minutes - 04/22, 17:00 UTC through 04/29, 11:20 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.
-Syed

Initial Update: Wednesday, 29 April 2020 10:27 UTC

We continue to investigate issues within Azure Metric Alerts. Some customers continue to experience missing alerts on SQL resources for alert rules that were created before 04/23 12:00 UTC in Public cloud, US Gov cloud, China Gov cloud. Initial findings indicate that the problem began at 04/22 ~17.00 UTC.

  • Work Around: None
  • Next Update: Before 04/29 14:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Syed

Initial Update: Wednesday, 29 April 2020 05:48 UTC

We continue to investigate issues within Azure Metric Alerts. Some customers continue to experience missing alerts on SQL resources for alert rules that were created before 04/23 12:00 UTC in Public cloud, US Gov cloud, China Gov cloud. Initial findings indicate that the problem began at 04/22 ~17.00 UTC.

  • Work Around: None
  • Next Update: Before 04/29 10:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Syed