Home
%3CLINGO-SUB%20id%3D%22lingo-sub-880295%22%20slang%3D%22en-US%22%3EExperiencing%20issues%20with%20Metric%20Alerts%20in%20Log%20Analytics%20for%20North%20Europe%20Region%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-880295%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%2028%20September%202019%2002%3A19%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2009%2F28%2C%2001%3A50%20UTC.Our%20logs%20show%20the%20incident%20started%20on%2009%2F27%2C04%3A00%20UTC%20and%20that%20during%20the%2021%20hours%20and%2050%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20a%20subset%20of%20customers%20in%20North%20Europe%20region%20using%20Log%20Analytics%20may%20have%20experienced%20issues%20with%20metric%20alerts%20not%20being%20delivered%20or%20may%20have%20received%20false%20positive%20alerts.%3CBR%20%2F%3E%3CUL%3E%0A%20%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20increase%20on%20load%20on%20the%20dependent%20service.%3C%2FLI%3E%0A%20%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2021%20Hours%20%26amp%3B%2050%20minutes%20-%2009%2F27%2C%2004%3A00%20UTC%20through%2009%2F28%2C%2001%3A50%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-Jayadev%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%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Saturday%2C%2028%20September%202019%2001%3A20%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Metric%20Alerts%20and%20are%20actively%20investigating.%20Customers%20using%20Log%20Analytics%20in%20North%20Europe%20region%20may%20experience%20issues%20with%20metric%20alerts%20either%20not%20being%20delivered%20or%20may%20receive%20false%20alerts.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2009%2F28%2005%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jayadev%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-880295%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Saturday, 28 September 2019 02:19 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/28, 01:50 UTC.Our logs show the incident started on 09/27,04:00 UTC and that during the 21 hours and 50 minutes that it took to resolve the issue a subset of customers in North Europe region using Log Analytics may have experienced issues with metric alerts not being delivered or may have received false positive alerts.
  • Root Cause: The failure was due to increase on load on the dependent service.
  • Incident Timeline: 21 Hours & 50 minutes - 09/27, 04:00 UTC through 09/28, 01:50 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.

-Jayadev

Initial Update: Saturday, 28 September 2019 01:20 UTC

We are aware of issues within Metric Alerts and are actively investigating. Customers using Log Analytics in North Europe region may experience issues with metric alerts either not being delivered or may receive false alerts.
  • Next Update: Before 09/28 05:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jayadev