%3CLINGO-SUB%20id%3D%22lingo-sub-1488652%22%20slang%3D%22en-US%22%3EManagement%20operations%20failures%20for%20Metric%20Alerts%20rules%20on%20Log%20Analytics%20Resources-%2006%2F25%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1488652%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%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Thursday%2C%2025%20June%202020%2010%3A34%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%206%2F25%2C%2009%3A25%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%206%2F23%2C%2010%3A30%20UTC%20and%20that%20during%20the%201%20day%2C%2022%20hours%20and%2055%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20experienced%20failures%20in%20creating%2C%20deleting%20or%20updating%20metric%20alert%20rules%20in%20Log%20Analytics%20Resources%20in%20multiple%20regions.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20dependent%20services.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20day%2C%2022%20Hours%20%26amp%3B%2055%20minutes%20-%206%2F23%2C%2010%3A30%20UTC%20through%206%2F25%2C%2009%3A25%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Metric%20Alerts%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Madhuri%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%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1488652%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 25 June 2020 10:34 UTC

We've confirmed that all systems are back to normal with no customer impact as of 6/25, 09:25 UTC. Our logs show the incident started on 6/23, 10:30 UTC and that during the 1 day, 22 hours and 55 minutes that it took to resolve the issue some of customers experienced failures in creating, deleting or updating metric alert rules in Log Analytics Resources in multiple regions.
  • Root Cause: The failure was due to an issue in one of our dependent services.
  • Incident Timeline: 1 day, 22 Hours & 55 minutes - 6/23, 10:30 UTC through 6/25, 09:25 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Madhuri