Home
%3CLINGO-SUB%20id%3D%22lingo-sub-821838%22%20slang%3D%22en-US%22%3EExperiencing%20issues%20while%20creating%20workspace%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2008%2F25%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-821838%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Sunday%2C%2025%20August%202019%2014%3A02%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2008%2F25%2C%2013%3A08%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F25%2C%2010%3A53%20UTC%20and%20that%20during%20the%202%20hours%20and%2015%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20~60%26nbsp%3B%20customers%20experience%20issues%20while%20creating%20new%20workspace%20for%20Azure%20Log%20Analytics%20in%20Azure%20Portal.%3CBR%20%2F%3E%3CUL%3E%0A%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20our%20backend%20services.%3C%2FLI%3E%0A%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20%26amp%3B%2015%20minutes%20-%2008%2F25%2C%2010%3A53%20UTC%20through%26nbsp%3B%2008%2F25%2C%2013%3A08%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Anmol%3C%2FDIV%3E%0A%3CHR%20%2F%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Sunday%2C%2025%20August%202019%2012%3A45%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customer%20may%20experience%20issues%20while%20creating%20new%20workspace%20for%20Azure%20Log%20Analytics%20in%20Azure%20Portal%3CBR%20%2F%3E%3CUL%3E%0A%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3ANone%3C%2FLI%3E%0A%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2008%2F25%2015%3A00%20UTC%3C%2FLI%3E%0A%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Anmol%3C%2FDIV%3E%0A%3CHR%20%2F%3E%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-821838%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Sunday, 25 August 2019 14:02 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/25, 13:08 UTC. Our logs show the incident started on 08/25, 10:53 UTC and that during the 2 hours and 15 minutes that it took to resolve the issue ~60  customers experience issues while creating new workspace for Azure Log Analytics in Azure Portal.
  • Root Cause: The failure was due to one of our backend services.
  • Incident Timeline: 2 Hours & 15 minutes - 08/25, 10:53 UTC through  08/25, 13:08 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Anmol

Initial Update: Sunday, 25 August 2019 12:45 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customer may experience issues while creating new workspace for Azure Log Analytics in Azure Portal
  • Work Around:None
  • Next Update: Before 08/25 15:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Anmol