Home
%3CLINGO-SUB%20id%3D%22lingo-sub-771433%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Metric%20Alerts%20-%2007%2F24%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-771433%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%2024%20July%202019%2012%3A04%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%207%2F24%2C%2011%3A48%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%207%2F24%2C%2009%3A39%20UTC%20and%20that%20during%20the%202%20hours%20and%209%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2030%25%20of%20customers%20might%20have%20experienced%20issues%20with%20Metric%20Alerts%20not%20evaluating.%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%202%20Hours%20%26amp%3B%209%20minutes%20-%207%2F24%2C%2009%3A39%20UTC%20through%207%2F24%2C%2011%3A48%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%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-771433%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-772485%22%20slang%3D%22en-US%22%3ERe%3A%20Experiencing%20Alerting%20failure%20for%20Metric%20Alerts%20-%2007%2F24%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-772485%22%20slang%3D%22en-US%22%3Estill%20have%20the%20issue%20in%20west%20europe%20region%2C%20azure%20monitor%20and%20aks%20metric%2C%20i%20still%20receive%20mail%20notification%20right%20now%3C%2FLINGO-BODY%3E
Final Update: Wednesday, 24 July 2019 12:04 UTC

We've confirmed that all systems are back to normal with no customer impact as of 7/24, 11:48 UTC. Our logs show the incident started on 7/24, 09:39 UTC and that during the 2 hours and 9 minutes that it took to resolve the issue 30% of customers might have experienced issues with Metric Alerts not evaluating.
  • Root Cause: The failure was due to an issue in one of our dependent services.
  • Incident Timeline: 2 Hours & 9 minutes - 7/24, 09:39 UTC through 7/24, 11:48 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Madhuri

1 Comment
Occasional Visitor
still have the issue in west europe region, azure monitor and aks metric, i still receive mail notification right now