Home
%3CLINGO-SUB%20id%3D%22lingo-sub-872301%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20issue%20in%20Metric%20alerts%20-%2009%2F24%20-%20Mitigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-872301%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%3EUpdate%3C%2FU%3E%3A%20Wednesday%2C%2025%20September%202019%2022%3A45%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20identified%20as%20a%20code-related%20issue%20impacting%20classic%20alert%20rules%20that%20were%20configured%20prior%20to%202017.%20To%20address%20the%20issue%20a%20hotfix%20has%20been%20tested%20and%20validated%20in%20the%20pre-production%20environment.%20As%20the%20fix%20is%20somewhat%20complex%2C%20it%20will%20be%20deployed%20to%20all%20regions%20over%20the%20next%205%20business%20days.%20Some%20customers%20may%20continue%20to%20experience%20issues%20with%20classic%20alert%20rules%20not%20delivering%20notifications%20until%20the%20deployment%20is%20completed%20to%20all%20regions.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E-Jayadev%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EUpdate%3C%2FU%3E%3A%20Wednesday%2C%2025%20September%202019%2021%3A11%20UTC%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Metric%20alerts.Root%20cause%20was%20determined%20to%20be%20an%20issue%20with%20alerts%20created%20prior%20to%202017%20not%20having%20a%20required%20field.Some%20customers%20continue%20to%20experience%20issues%20with%20classic%20alert%20rules%20not%20delivering%20notifications.We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2Cinitial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F08%2F19%20~00%3A00%20UTC.We%20currently%20have%20no%20estimate%20for%20resolution.%3CBR%20%2F%3E%3CUL%20style%3D%22text-align%3A%20left%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20text-transform%3A%20none%3B%20text-indent%3A%200px%3B%20letter-spacing%3A%20normal%3B%20font-family%3A%20%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20margin-top%3A%200px%3B%20margin-bottom%3A%2010px%3B%20word-spacing%3A%200px%3B%20white-space%3A%20normal%3B%20box-sizing%3A%20border-box%3B%20orphans%3A%202%3B%20-webkit-text-stroke-width%3A%200px%3B%22%3E%3CLI%20style%3D%22box-sizing%3A%20border-box%3B%22%3E%3CFONT%20face%3D%22%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%22%3E%3CFONT%20face%3D%22%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%22%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2009%2F26%2009%3A30%20UTC%3C%2FFONT%3E%3CSPAN%20style%3D%22text-align%3A%20left%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20text-transform%3A%20none%3B%20text-indent%3A%200px%3B%20letter-spacing%3A%20normal%3B%20font-family%3A%20%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20word-spacing%3A%200px%3B%20display%3A%20inline%20!important%3B%20white-space%3A%20normal%3B%20orphans%3A%202%3B%20float%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%22%3E%3C%2FSPAN%3E%3C%2FFONT%3E%26nbsp%3B%3C%2FLI%3E%3C%2FUL%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E-Jayadev%3C%2FSPAN%3E%3CB%3E%3C%2FB%3E%3CI%3E%3C%2FI%3E%3CU%3E%3C%2FU%3E%3CSUB%3E%3C%2FSUB%3E%3CSUP%3E%3C%2FSUP%3E%3CSTRIKE%3E%3C%2FSTRIKE%3E%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%20Wednesday%2C%2025%20September%202019%2017%3A16%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3EWe%20continue%20to%20investigate%20issues%20within%20Metric%20alerts.Root%20cause%20was%20determined%20to%20be%20an%20issue%20with%20alerts%20created%20prior%20to%202017%20not%20having%20a%20required%20field.Some%20customers%20continue%20to%20experience%20issues%20with%20classic%20alert%20rules%20not%20delivering%20notifications.We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2Cinitial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F08%2F19%20~00%3A00%20UTC.We%20currently%20have%20no%20estimate%20for%20resolution.%3C%2FSPAN%3E%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2009%2F25%2021%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Jayadev%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%20Wednesday%2C%2025%20September%202019%2013%3A32%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Metric%20alerts.Root%20cause%20was%20determined%20to%20be%20an%20issue%20with%20alerts%20created%20prior%20to%202017%20not%20having%20a%20required%20field.Some%20customers%20continue%20to%20experience%20issues%20with%20classic%20alert%20rules%20not%20delivering%20notifications.We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2Cinitial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F08%2F19%20~00%3A00%20UTC.We%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%2009%2F25%2018%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Naresh%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%20Wednesday%2C%2025%20September%202019%2006%3A13%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Metric%20alerts.Root%20cause%20was%20determined%20to%20be%20an%20issue%20with%20alerts%20created%20prior%20to%202017%20not%20having%20a%20required%20field.Some%20customers%20continue%20to%20experience%20issues%20with%20classic%20alert%20rules%20not%20delivering%20notifications.We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2Cinitial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F08%2F19%20~00%3A00%20UTC.We%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%2009%2F25%2012%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Naresh%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%20Tuesday%2C%2024%20September%202019%2018%3A38%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Metric%20alerts.Root%20cause%20was%20determined%20to%20be%20an%20issue%20with%20alerts%20created%20prior%20to%202017%20not%20having%20a%20required%20field.Some%20customers%20continue%20to%20experience%20issues%20with%20classic%20alert%20rules%20not%20delivering%20notifications.We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2Cinitial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F08%2F19%20~00%3A00%20UTC.We%20currently%20have%20no%20estimate%20for%20resolution.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2009%2F25%2001%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Jayadev%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%20Tuesday%2C%2024%20September%202019%2015%3A03%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Metric%20alerts%20and%20are%20actively%20investigating.Some%20customers%20may%20experience%20issue%20running%20classic%20alert%20rules.%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%2009%2F24%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-Naresh%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%2FDIV%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-872301%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 11 October 2019 09:08 UTC

We've confirmed that all systems are back to normal with no customer impact as of 10/03, 16:45 UTC. Our logs show the incident started on 08/24, 14:06 UTC and that during the ~936 hours that it took to resolve the issue some of customers experienced issues with classic alert rules not delivering notifications.
  • Root Cause: The failure was due to issue in one of our backend service.
  • Incident Timeline: 936 Hours - 08/24, 14:06 UTC through 10/03, 16:45 UTC
We understand that customers rely on Metric alerts as a critical service and apologize for any impact this incident caused.

-Naresh

Update: Wednesday, 25 September 2019 22:45 UTC

Root cause has been identified as a code-related issue impacting classic alert rules that were configured prior to 2017. To address the issue a hotfix has been tested and validated in the pre-production environment. As the fix is somewhat complex, it will be deployed to all regions over the next 5 business days. Some customers may continue to experience issues with classic alert rules not delivering notifications until the deployment is completed to all regions.

-Jayadev

Update: Wednesday, 25 September 2019 21:11 UTC

We continue to investigate issues within Metric alerts.Root cause was determined to be an issue with alerts created prior to 2017 not having a required field.Some customers continue to experience issues with classic alert rules not delivering notifications.We are working to establish the start time for the issue,initial findings indicate that the problem began at 07/08/19 ~00:00 UTC.We currently have no estimate for resolution.
  • Next Update: Before 09/26 09:30 UTC 
-Jayadev

Update: Wednesday, 25 September 2019 17:16 UTC

We continue to investigate issues within Metric alerts.Root cause was determined to be an issue with alerts created prior to 2017 not having a required field.Some customers continue to experience issues with classic alert rules not delivering notifications.We are working to establish the start time for the issue,initial findings indicate that the problem began at 07/08/19 ~00:00 UTC.We currently have no estimate for resolution.
  • Next Update: Before 09/25 21:30 UTC
-Jayadev

Update: Wednesday, 25 September 2019 13:32 UTC

We continue to investigate issues within Metric alerts.Root cause was determined to be an issue with alerts created prior to 2017 not having a required field.Some customers continue to experience issues with classic alert rules not delivering notifications.We are working to establish the start time for the issue,initial findings indicate that the problem began at 07/08/19 ~00:00 UTC.We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 09/25 18:00 UTC
-Naresh

Update: Wednesday, 25 September 2019 06:13 UTC

We continue to investigate issues within Metric alerts.Root cause was determined to be an issue with alerts created prior to 2017 not having a required field.Some customers continue to experience issues with classic alert rules not delivering notifications.We are working to establish the start time for the issue,initial findings indicate that the problem began at 07/08/19 ~00:00 UTC.We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 09/25 12:30 UTC
-Naresh

Update: Tuesday, 24 September 2019 18:38 UTC

We continue to investigate issues within Metric alerts.Root cause was determined to be an issue with alerts created prior to 2017 not having a required field.Some customers continue to experience issues with classic alert rules not delivering notifications.We are working to establish the start time for the issue,initial findings indicate that the problem began at 07/08/19 ~00:00 UTC.We currently have no estimate for resolution.
  • Next Update: Before 09/25 01:00 UTC
-Jayadev

Initial Update: Tuesday, 24 September 2019 15:03 UTC

We are aware of issues within Metric alerts and are actively investigating.Some customers may experience issue running classic alert rules.
  • Work Around: None
  • Next Update: Before 09/24 18:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Naresh