Experiencing Data Latency in Azure portal for Activity Log Alerts - 06/02 - Resolved

Published Jun 02 2020 03:29 AM 1,389 Views
Final Update: Wednesday, 03 June 2020 05:26 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/02, 22:00 UTC. Our logs show the incident started on 06/01, 15:00 UTC and that during the 1 day and 7 hours that it took to resolve the issue, some customers may have experienced delayed alerts globally. Alerts will eventually fire, however they may be up to 20 minutes delayed.
  • Root Cause: Engineers determined that some instances of a back-end service became unhealthy after reaching an operational threshold, causing throttling on a dependent service. This throttling resulted in the alert delays.
  • Incident Timeline: 1 Day  &7 Hours  - 06/01, 15:00 UTC through 06/02, 22:00 UTC
We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused.

-Anmol

Update: Tuesday, 02 June 2020 17:06 UTC

We continue to investigate issues within Activity Log Alerts. Root cause has been narrowed to a dependent service throttling issue which we are working on resolving. Some customers continue to experience delayed alerts globally. Alerts will eventually fire, however they may be up to 20 minutes delayed. The problem began at 6/01 15:00 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 06/03 05:00 UTC
-Jeff

Update: Tuesday, 02 June 2020 12:59 UTC

We continue to investigate issues within Activity Log Alerts. Root cause is not fully understood at this time. Some customers continue to experience delayed alerts globally. Alerts will eventually fire, however they may be up to 20 minutes delayed.  We are working to establish the start time for the issue, initial findings indicate that the problem began at 05/01 ~15:00 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 06/02 17:00 UTC
-Anmol

Initial Update: Tuesday, 02 June 2020 10:20 UTC

 We are aware of issues within Activity Log Alerts and are actively investigating. Some customers may experience delayed alerts. 
  • Work Around: None
  • Next Update: Before 06/02 13:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anmol

%3CLINGO-SUB%20id%3D%22lingo-sub-1433009%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20in%20Azure%20portal%20for%20Activity%20Log%20Alerts%20-%2006%2F02%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1433009%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%2003%20June%202020%2005%3A26%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2006%2F02%2C%2022%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F01%2C%2015%3A00%20UTC%20and%20that%20during%20the%201%20day%20and%207%20hours%20that%20it%20took%20to%20resolve%20the%20issue%2C%20some%20customers%20may%20have%20experienced%20delayed%20alerts%20globally.%20Alerts%20will%20eventually%20fire%2C%20however%20they%20may%20be%20up%20to%2020%20minutes%20delayed.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20Engineers%20determined%20that%20some%20instances%20of%20a%20back-end%20service%20became%20unhealthy%20after%20reaching%20an%20operational%20threshold%2C%20causing%20throttling%20on%20a%20dependent%20service.%20This%20throttling%20resulted%20in%20the%20alert%20delays.%3C%2FLI%3E%0A%20%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Day%26nbsp%3B%20%26amp%3B7%20Hours%26nbsp%3B%20-%2006%2F01%2C%2015%3A00%20UTC%20through%2006%2F02%2C%2022%3A00%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Activity%20Log%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Anmol%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%2002%20June%202020%2017%3A06%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Activity%20Log%20Alerts.%20Root%20cause%20has%20been%20narrowed%20to%20a%20dependent%20service%20throttling%20issue%20which%20we%20are%20working%20on%20resolving.%20Some%20customers%20continue%20to%20experience%20delayed%20alerts%20globally.%26nbsp%3BAlerts%20will%20eventually%20fire%2C%20however%20they%20may%20be%20up%20to%2020%20minutes%20delayed.%26nbsp%3BThe%20problem%20began%20at%206%2F01%2015%3A00%20UTC.%20We%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%2006%2F03%2005%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Jeff%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%2002%20June%202020%2012%3A59%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Activity%20Log%20Alerts.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20continue%20to%20experience%20delayed%20alerts%20globally.%26nbsp%3BAlerts%20will%20eventually%20fire%2C%20however%20they%20may%20be%20up%20to%2020%20minutes%20delayed.%26nbsp%3B%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2005%2F01%20~15%3A00%20UTC.%20We%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%2006%2F02%2017%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Anmol%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%2002%20June%202020%2010%3A20%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3BWe%20are%20aware%20of%20issues%20within%20Activity%20Log%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20delayed%20alerts.%26nbsp%3B%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%2006%2F02%2013%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Anmol%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-1433009%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Jun 02 2020 10:34 PM
Updated by: