Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1409484%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Azure%20Monitor%20Alerts%20-%2005%2F21%20-%20Investigating%20-%20AzureChina%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1409484%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%20Thursday%2C%2021%20May%202020%2018%3A10%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2005%2F21%2C%2018%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2005%2F21%2C%2012%3A30%20UTC%20and%20during%20the%20time%20it%20took%20to%20resolve%20the%20issue%20customers%20experienced%20failure%20in%20receiving%20Azure%20Monitor%20Alerts%20China%20East%202%20and%20China%20North%202%20regions.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20recent%20deployment%20that%20impacted%20the%20underlying%20alert%20notification%20functionality.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%205%20Hours%20%26amp%3B%205%20minutes%20-%205%2F21%2C%2012%3A30%20UTC%20through%2005%2F21%2C%2017%3A35%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-chandar%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%3EFinal%20Update%3C%2FU%3E%3A%20Thursday%2C%2021%20May%202020%2018%3A10%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2005%2F21%2C%2018%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2005%2F21%2C%2012%3A30%20UTC%20and%20during%20the%20time%20it%20took%20to%20resolve%20the%20issue%20customers%20experienced%20failure%20in%20receiving%20Azure%20Monitor%20Alerts%20China%20East%202%20and%20China%20North%202%20regions.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20recent%20deployment%20that%20impacted%20the%20underlying%20alert%20notification%20functionality.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%205%20Hours%20%26amp%3B%205%20minutes%20-%205%2F21%2C%2012%3A30%20UTC%20through%2005%2F21%2C%2017%3A35%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-chandar%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%20Thursday%2C%2021%20May%202020%2017%3A15%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20with%20Azure%20Monitor%20Alerts%20in%20Azure%20China%20(East2%20and%20North2%20regions)%20and%20are%20actively%20investigating.%20Customers%20may%20miss%20receiving%20alerts%20for%20the%20rules%20that%20may%20have%20been%20configured.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2005%2F21%2019%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-chandar%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1409484%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 21 May 2020 18:10 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/21, 18:00 UTC. Our logs show the incident started on 05/21, 12:30 UTC and during the time it took to resolve the issue customers experienced failure in receiving Azure Monitor Alerts China East 2 and China North 2 regions.
  • Root Cause: The failure was due to recent deployment that impacted the underlying alert notification functionality.
  • Incident Timeline: 5 Hours & 5 minutes - 5/21, 12:30 UTC through 05/21, 17:35 UTC
We understand that customers rely on Azure Monitor Alerts as a critical service and apologize for any impact this incident caused.

-chandar

Final Update: Thursday, 21 May 2020 18:10 UTC

We've confirmed that all systems are back to normal with no customer impact as of 05/21, 18:00 UTC. Our logs show the incident started on 05/21, 12:30 UTC and during the time it took to resolve the issue customers experienced failure in receiving Azure Monitor Alerts China East 2 and China North 2 regions.
  • Root Cause: The failure was due to recent deployment that impacted the underlying alert notification functionality.
  • Incident Timeline: 5 Hours & 5 minutes - 5/21, 12:30 UTC through 05/21, 17:35 UTC
We understand that customers rely on Azure Monitor Alerts as a critical service and apologize for any impact this incident caused.

-chandar

Initial Update: Thursday, 21 May 2020 17:15 UTC

We are aware of issues with Azure Monitor Alerts in Azure China (East2 and North2 regions) and are actively investigating. Customers may miss receiving alerts for the rules that may have been configured.
  • Work Around
  • Next Update: Before 05/21 19:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-chandar