%3CLINGO-SUB%20id%3D%22lingo-sub-1271020%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20in%20Azure%20portal%20for%20Activity%20Log%20Alerts%20-%2004%2F01%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1271020%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%20Saturday%2C%2004%20April%202020%2012%3A58%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2004%2F03%2C%2021%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2003%2F30%2C%2023%3A10%20UTC%20and%20that%20during%20the%203%20days%2021%20hours%20%26amp%3B%2050%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20might%20have%20experienced%20issue%20with%20delay%20in%20Active%20Log%20Alert%20and%20Metric%20Alerts.%3C%2FDIV%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20the%20back%20end%20service.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%203%20days%2021%20Hours%20%26amp%3B%2050%20minutes%20-%2003%2F30%2C%2023%3A10%20UTC%20through%2004%2F03%2C%2021%3A00%20UTC%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-Syed%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%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Thursday%2C%2003%20April%202020%2010%3A30%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Alert%20management%20platform%20and%20are%20actively%20investigating.%20Some%20customers%20using%20Azure%20metric%20alerts%20and%20Azure%20Activity%20Log%20Alerts%20may%20have%20experiencing%20delays%20in%20receiving%20their%20Alerts.%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%2004%2F04%2013%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%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%20Wednesday%2C%2001%20April%202020%2015%3A59%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Alert%20management%20platform%20and%20are%20actively%20investigating.%20Some%20customers%20using%20Azure%20metric%20alerts%20and%20Azure%20Activity%20Log%20Alerts%20may%20have%20experiencing%20delays%20in%20receiving%20their%20Alerts.%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%2004%2F02%2010%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%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%20Wednesday%2C%2001%20April%202020%2013%3A08%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Alert%20management%20platform%20and%20are%20actively%20investigating.%20Some%20customers%20using%20Azure%20metric%20alerts%20and%20Azure%20Activity%20Log%20Alerts%20may%20have%20experiencing%20delays%20in%20receiving%20their%20Alerts.%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%2004%2F01%2016%3A30%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%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%20Wednesday%2C%2001%20April%202020%2011%3A09%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Alert%20management%20platform%20and%20are%20actively%20investigating.%20Some%20customers%20using%20Azure%20metric%20alerts%20and%20Azure%20Activity%20Log%20Alerts%20may%20have%20experiencing%20delays%20in%20receiving%20their%20Alerts.%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%2004%2F01%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-Syed%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%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-1271020%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Saturday, 04 April 2020 12:58 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/03, 21:00 UTC. Our logs show the incident started on 03/30, 23:10 UTC and that during the 3 days 21 hours & 50 minutes that it took to resolve the issue some customers might have experienced issue with delay in Active Log Alert and Metric Alerts.
  • Root Cause: The failure was due to one of the back end service.
  • Incident Timeline: 3 days 21 Hours & 50 minutes - 03/30, 23:10 UTC through 04/03, 21: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: Thursday, 03 April 2020 10:30 UTC

We are aware of issues within Alert management platform and are actively investigating. Some customers using Azure metric alerts and Azure Activity Log Alerts may have experiencing delays in receiving their Alerts.
  • Work Around: None
  • Next Update: Before 04/04 13:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Syed

Initial Update: Wednesday, 01 April 2020 15:59 UTC

We are aware of issues within Alert management platform and are actively investigating. Some customers using Azure metric alerts and Azure Activity Log Alerts may have experiencing delays in receiving their Alerts.
  • Work Around: None
  • Next Update: Before 04/02 10:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Syed

Initial Update: Wednesday, 01 April 2020 13:08 UTC

We are aware of issues within Alert management platform and are actively investigating. Some customers using Azure metric alerts and Azure Activity Log Alerts may have experiencing delays in receiving their Alerts.
  • Work Around: None
  • Next Update: Before 04/01 16:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Syed

Initial Update: Wednesday, 01 April 2020 11:09 UTC

We are aware of issues within Alert management platform and are actively investigating. Some customers using Azure metric alerts and Azure Activity Log Alerts may have experiencing delays in receiving their Alerts.
  • Work Around: None
  • Next Update: Before 04/01 13:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Syed