%3CLINGO-SUB%20id%3D%22lingo-sub-1451164%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Activity%20Log%20Alerts%20-%2006%2F09%20-%20Investigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1451164%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%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Tuesday%2C%2009%20June%202020%2014%3A38%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%3E%3CDIV%3EWe%20are%20aware%20of%20the%20issue%20with%20ITSM%20action%20that%20Since%2019%20May%202020%20some%20of%20ITSM%20Connector%20customers%20fail%20to%20receive%20their%20Azure%20Alerts%20into%20external%20ITSM%20systems.This%20outage%20affects%20customers%20that%20have%20added%20a%20new%20ITSM%20action%20or%20updated%20their%20existing%20ITSM%20action%20via%20Azure%20Portal%20since%2019%20May%202020.The%20fix%20for%20the%20broken%20ITSM%20action%20management%20experience%20was%20deployed%20on%2009%20June%202020.%3C%2FDIV%3E%3CDIV%3EWe%20are%20also%20deploying%20a%20fix%20for%20the%20corrupted%20ITSM%20actions%2C%20to%20be%20expected%20by%2015%20June%202020.%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20Customers%20can%20re-create%20the%20corrupted%20actions.%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F10%2015%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%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1451164%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 10 June 2020 09:09 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/09, 20:00 UTC. Our logs show the incident started on 05/19, 00:00 UTC and that during the 21 days and 20 hours that it took to resolve the issue some customers fail to receive their Azure Alerts into external ITSM systems.This outage might have affected customers that have added a new ITSM action or updated their existing ITSM action via Azure Portal since 19 May 2020 issue.
  • Root Cause: The failure was due to one of our back end services.
  • Incident Timeline: 21 days 20 Hours  - 05/19, 00:00 UTC through 06/09, 20:00 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused.
-Syed

Initial Update: Tuesday, 09 June 2020 14:38 UTC

We are aware of the issue with ITSM action that Since 19 May 2020 some of ITSM Connector customers fail to receive their Azure Alerts into external ITSM systems.This outage affects customers that have added a new ITSM action or updated their existing ITSM action via Azure Portal since 19 May 2020.The fix for the broken ITSM action management experience was deployed on 09 June 2020.
We are also deploying a fix for the corrupted ITSM actions, to be expected by 15 June 2020. 
  • Work Around: Customers can re-create the corrupted actions.
  • Next Update: Before 06/10 15:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Syed