Home
%3CLINGO-SUB%20id%3D%22lingo-sub-357928%22%20slang%3D%22en-US%22%3EExperiencing%20Notification%20failure%20for%20Activity%20Log%20Alerts%20-%2002%2F27%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-357928%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%26nbsp%3BWednesday%2C%2028%20February%202019%2003%3A08%20UTC%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F28%2002%3A38%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F26%2C%2021%3A00%20UTC%20and%20that%20during%20the%20~29hr%2038m%20that%20it%20took%20to%20resolve%20the%20issue%20few%20customers%20would%20have%20experienced%20Notification%20miss%20from%20Azure%20Activity%20Log%20Alerts.%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%3CUL%3E%0A%3CLI%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%0A%3CLI%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2029%20Hours%20%26amp%3B%2038%20minutes%20-%2002%2F26%2C%2021%3A00%20UTC%20through%2002%2F28%2002%3A38%20UTC%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Activity%20Log%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E-Vishal%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EUpdate%3C%2FU%3E%3A%20Thursday%2C%2028%20February%202019%2000%3A56%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20an%20issue%20with%20one%20of%20the%20dependent%20services%20which%20was%20impacting%20notification%20misses%20for%20Activity%20Log%20alerts.%20To%20address%20this%20issue%20we%20are%20rolling%20back%20the%20configuration%20changes.%20Some%20customers%20may%20experience%20notification%20miss%20from%20Activity%20log%20alerts%20and%20we%20estimate%20in%20next%20~2%20hours%20the%20notification%20miss%20issue%20to%20be%20addressed%20for%20all%20customers.%3CBR%20%2F%3E%3CUL%3E%0A%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20NA%3C%2FLI%3E%0A%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2002%2F28%2004%3A00%20UTC%3C%2FLI%3E%0A%3C%2FUL%3E-Vishal%3C%2FDIV%3E%0A%3CHR%20%2F%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Wednesday%2C%2027%20February%202019%2023%3A22%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20Notification%20issues%20within%20Activity%20Log%20alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20missing%20notification%20for%20the%20Activity%20Log%20Alerts.%3CBR%20%2F%3E%3CUL%3E%0A%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20NA%3C%2FLI%3E%0A%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2002%2F28%2001%3A30%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Vishal%3C%2FDIV%3E%0A%3CHR%20%2F%3E%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-357928%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 28 February 2019 03:08 UTC
 
We've confirmed that all systems are back to normal with no customer impact as of 02/28 02:38 UTC. Our logs show the incident started on 02/26, 21:00 UTC and that during the ~29hr 38m that it took to resolve the issue few customers would have experienced Notification miss from Azure Activity Log Alerts.
  • Root Cause: The failure was due to issues in one of our dependent services.
  • Incident Timeline: 29 Hours & 38 minutes - 02/26, 21:00 UTC through 02/28 02:38 UTC
We understand that customers rely on Azure Activity Log Alerts as a critical service and apologize for any impact this incident caused.
-Vishal
 
Update: Thursday, 28 February 2019 00:56 UTC

Root cause has been isolated to an issue with one of the dependent services which was impacting notification misses for Activity Log alerts. To address this issue we are rolling back the configuration changes. Some customers may experience notification miss from Activity log alerts and we estimate in next ~2 hours the notification miss issue to be addressed for all customers.
  • Work Around: NA
  • Next Update: Before 02/28 04:00 UTC
-Vishal

Initial Update: Wednesday, 27 February 2019 23:22 UTC

We are aware of Notification issues within Activity Log alerts and are actively investigating. Some customers may experience missing notification for the Activity Log Alerts.
  • Work Around: NA
  • Next Update: Before 02/28 01:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Vishal