%3CLINGO-SUB%20id%3D%22lingo-sub-1142915%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2001%2F31%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1142915%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%20Friday%2C%2031%20January%202020%2015%3A44%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%2F31%2C%2015%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F30%2C%2018%3A00%20UTC%20and%20that%20during%20the%2021%20hours%20and%2030%20min%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20False%20Alerts%20on%20Availability%20Test%26nbsp%3B%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3Ein%26nbsp%3B%3C%2FSPAN%3EWest%20Europe%20region.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20metric%20configuration%20change%20after%20the%20deployment.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2021%20Hours%20%26amp%3B%2030%20minutes%20-%2001%2F30%2C%2018%3A30%20UTC%20through%2001%2F31%2C%2015%3A30%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%3CBR%20%2F%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Friday%2C%2031%20January%202020%2014%3A19%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Application%20Insights%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20False%20Alerts%20on%20Availability%20Test%20%3CSPAN%20style%3D%22font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3Ein%26nbsp%3B%3C%2FSPAN%3EWest%20Europe%20region.%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%2001%2F31%2018%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Anusha%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-1142915%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 31 January 2020 15:44 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/31, 15:30 UTC. Our logs show the incident started on 01/30, 18:00 UTC and that during the 21 hours and 30 min that it took to resolve the issue some customers may have experienced False Alerts on Availability Test in West Europe region.
  • Root Cause: The failure was due to metric configuration change after the deployment.
  • Incident Timeline: 21 Hours & 30 minutes - 01/30, 18:30 UTC through 01/31, 15:30 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Anusha

Initial Update: Friday, 31 January 2020 14:19 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers may experience False Alerts on Availability Test in West Europe region.
  • Work Around: None
  • Next Update: Before 01/31 18:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anusha