Experiencing Alerting failure for Log Search Alerts - 07/26 - Resolved

Published Jul 26 2021 08:20 AM 1,025 Views
Final Update: Monday, 26 July 2021 15:12 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/26, 14:30 UTC. Our logs show the incident started on 07/26, 13:30 UTC and that during the 1 hour that it took to resolve the issue some of the customers using Azure monitor may have received failure notifications while accessing or performing service management operations such as create, update, delete for Azure Log Search Alert Rules.
  • Root Cause: The failure was due to a dependent backend component failure.
  • Incident Timeline: 1 Hour - 07/26, 13:30 UTC through 07/26, 14:30 UTC
We understand that customers rely on Azure monitor as a critical service and apologize for any impact this incident caused.

-Soumyajeet

%3CLINGO-SUB%20id%3D%22lingo-sub-2587318%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Log%20Search%20Alerts%20-%2007%2F26%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2587318%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%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%20Monday%2C%2026%20July%202021%2015%3A12%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2007%2F26%2C%2014%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2007%2F26%2C%2013%3A30%20UTC%20and%20that%20during%20the%201%20hour%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20the%20customers%20using%20Azure%20monitor%20may%20have%20received%20failure%20notifications%20while%20accessing%20or%20performing%20service%20management%20operations%20such%20as%20create%2C%20update%2C%20delete%20for%20Azure%20Log%20Search%20Alert%20Rules.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20dependent%20backend%20component%20failure.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20-%2007%2F26%2C%2013%3A30%20UTC%20through%2007%2F26%2C%2014%3A30%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20monitor%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Soumyajeet%3CBR%20%2F%3E%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
Version history
Last update:
‎Jul 26 2021 08:27 AM
Updated by: