%3CLINGO-SUB%20id%3D%22lingo-sub-353402%22%20slang%3D%22en-US%22%3EARM%20deployment%20issue%20for%20Log%20search%20alerts%20-%2001%2F31%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-353402%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Jan%2031%2C%202019%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CDIV%3E%0A%20%20%20%3CDIV%3E%0A%20%20%20%20%3CDIV%3E%0A%20%20%20%20%20%3CDIV%3EFinal%20Update%3A%20Thursday%2C%2031%20January%202019%2000%3A42%20UTC%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20We've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2030%20January%202019%2018%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2024%20January%202019%2000%3A00%20UTC%20and%20that%20during%20the%206%20days%203%20hours%2030%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%205%25%20of%20customers%20would%20have%20seen%20failures%20while%20creating%20alerts%20through%20an%20ARM%20template.%20%3CBR%20%2F%3E%3CUL%3E%0A%20%20%20%20%20%20%20%3CLI%3ERoot%20Cause%3A%20The%20failure%20was%20due%20to%20the%20issue%20with%20one%20of%20backend%20system.%3C%2FLI%3E%0A%20%20%20%20%20%20%20%3CLI%3EIncident%20Timeline%3A%206%20days%203%20Hours%20%26amp%3B%2030%20minutes%20-%26nbsp%3B%2024%20January%202019%2000%3A00%20UTC%20through%26nbsp%3B30%20January%202019%2018%3A00%20UTC.%3C%2FLI%3E%0A%20%20%20%20%20%20%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20and%20Log%20Analytics%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20-Leela%20%3CBR%20%2F%3E%3C%2FDIV%3E%0A%20%20%20%20%3C%2FDIV%3E%0A%20%20%20%3C%2FDIV%3E%0A%20%20%3C%2FDIV%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-353402%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Jan%2031%2C%202019%20Final%20Update%3A%20Thursday%2C%2031%20January%202019%2000%3A42%20UTCWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2030%20January%202019%2018%3A00%20UTC.%3C%2FLINGO-TEASER%3E
First published on MSDN on Jan 31, 2019
Final Update: Thursday, 31 January 2019 00:42 UTC

We've confirmed that all systems are back to normal with no customer impact as of 30 January 2019 18:00 UTC. Our logs show the incident started on 24 January 2019 00:00 UTC and that during the 6 days 3 hours 30 minutes that it took to resolve the issue 5% of customers would have seen failures while creating alerts through an ARM template.
  • Root Cause: The failure was due to the issue with one of backend system.
  • Incident Timeline: 6 days 3 Hours & 30 minutes -  24 January 2019 00:00 UTC through 30 January 2019 18:00 UTC.
We understand that customers rely on Application Insights and Log Analytics as a critical service and apologize for any impact this incident caused.

-Leela