Home
%3CLINGO-SUB%20id%3D%22lingo-sub-672006%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20notification%20failure%20issue%20in%20Azure%20Portal%20-%2006%2F05%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-672006%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%2005%20June%202019%2023%3A58%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%20June%205th%202019%2C%2021%3A36%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%20June%205th%202019%2C%2015%3A00%20UTC%20and%20that%20during%20the%20time%20that%20it%20took%20to%20resolve%20the%20issue%20subset%20of%20customers%20would%20have%20missed%20receiving%20Alerting%20notifications.%26nbsp%3B%20Customers%20might%20be%20receiving%20these%20missed%20notifications%20in%20a%20delayed%20timeline%20as%20the%20system%20processes%20the%20backlog.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20performance%20issues%20of%20a%20downstream%20system%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3ELessons%20Learned%3C%2FU%3E%3A%20Chance%20of%20recurrence%20of%20this%20issue%20is%20low%2C%20and%20we%20will%20continue%20to%20monitor%20the%20system.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%20%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%3EJune%205th%202019%2C%2021%3A36%20UTC%3C%2FSPAN%3E%20through%20%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%3EJune%205th%202019%2C%2015%3A00%20UTC%3C%2FSPAN%3E%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-chandar.%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%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%22box-sizing%3A%20border-box%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%3CU%20style%3D%22box-sizing%3A%20border-box%3B%22%3EUpdate%3C%2FU%3E%3A%20Wednesday%2C%2005%20June%202019%2018%3A44%20UTC%3CBR%20style%3D%22box-sizing%3A%20border-box%3B%22%20%2F%3E%3CBR%20style%3D%22box-sizing%3A%20border-box%3B%22%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20downstream%20service%20which%20was%20impacting%20%3CSPAN%20style%3D%22background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20box-sizing%3A%20border-box%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20display%3A%20inline%3B%20float%3A%20none%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%3Ealerting%20%3C%2FSPAN%3Enotification%20for%20subset%20of%20customers.%20To%20address%20this%20issue%20we%20are%20in%20the%20process%20of%20rolling%20out%20a%20fix.%26nbsp%3B%20Some%20customers%20may%20experience%20notification%20failures%20and%20we%20estimate%201%20hour%20before%20all%20notification%20impacts%20are%20addressed.%3CBR%20style%3D%22box-sizing%3A%20border-box%3B%22%20%2F%3E%3CUL%20style%3D%22box-sizing%3A%20border-box%3B%20margin-bottom%3A%2010px%3B%20margin-top%3A%200px%3B%22%3E%3CLI%20style%3D%22box-sizing%3A%20border-box%3B%22%3E%3CU%20style%3D%22box-sizing%3A%20border-box%3B%22%3EWork%20Around%3C%2FU%3E%3A%20none%3C%2FLI%3E%3CLI%20style%3D%22box-sizing%3A%20border-box%3B%22%3E%3CU%20style%3D%22box-sizing%3A%20border-box%3B%22%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F05%2021%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Chandar.%3CBR%20style%3D%22box-sizing%3A%20border-box%3B%22%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-bottom-color%3A%20currentColor%3B%20border-bottom-style%3A%20none%3B%20border-bottom-width%3A%200px%3B%20border-image-outset%3A%200%3B%20border-image-repeat%3A%20stretch%3B%20border-image-slice%3A%20100%25%3B%20border-image-source%3A%20none%3B%20border-image-width%3A%201%3B%20border-left-color%3A%20currentColor%3B%20border-left-style%3A%20none%3B%20border-left-width%3A%200px%3B%20border-right-color%3A%20currentColor%3B%20border-right-style%3A%20none%3B%20border-right-width%3A%200px%3B%20border-top-color%3A%20lightgray%3B%20border-top-style%3A%20solid%3B%20border-top-width%3A%201px%3B%20box-sizing%3A%20content-box%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%20height%3A%200px%3B%20letter-spacing%3A%20normal%3B%20margin-bottom%3A%2020px%3B%20margin-top%3A%2020px%3B%20orphans%3A%202%3B%20text-align%3A%20center%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%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-672006%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 05 June 2019 23:58 UTC

We've confirmed that all systems are back to normal with no customer impact as of June 5th 2019, 21:36 UTC. Our logs show the incident started on June 5th 2019, 15:00 UTC and that during the time that it took to resolve the issue subset of customers would have missed receiving Alerting notifications.  Customers might be receiving these missed notifications in a delayed timeline as the system processes the backlog.
  • Root Cause: The failure was due to a performance issues of a downstream system 
  • Lessons Learned: Chance of recurrence of this issue is low, and we will continue to monitor the system.
  • Incident Timeline: June 5th 2019, 21:36 UTC through June 5th 2019, 15:00 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-chandar.



Update: Wednesday, 05 June 2019 18:44 UTC

Root cause has been isolated to downstream service which was impacting alerting notification for subset of customers. To address this issue we are in the process of rolling out a fix.  Some customers may experience notification failures and we estimate 1 hour before all notification impacts are addressed.
  • Work Around: none
  • Next Update: Before 06/05 21:00 UTC
-Chandar.