%3CLINGO-SUB%20id%3D%22lingo-sub-1835416%22%20slang%3D%22en-US%22%3EExperiencing%20Workspace%20Creation%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2010%2F29%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1835416%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%20Thursday%2C%2029%20October%202020%2022%3A48%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EOur%20logs%20indicate%20the%20incident%20started%20on%2010%2F29%2C%2021%3A30%20UTC%20and%20that%20during%20the%201%20hour%20that%20it%20took%20to%20resolve%20the%20issue%20no%20customers%20experienced%20an%20issue%20trying%20to%20create%20a%20new%20workspace%20and%20receiving%20%22internal%20server%20error%22%20as%20a%20result.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20DNS%20limit%20being%20reached%20in%20China%20region.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%200%20minutes%20-%2010%2F29%2C%2021%3A30%20UTC%20through%2010%2F29%2C%2022%3A30%20UTC%3C%2FLI%3E%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-Jeff%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%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Thursday%2C%2029%20October%202020%2022%3A04%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20in%20the%20China%20region%20may%20experience%20an%20%22internal%20server%20error%22%20when%20trying%20to%20create%20a%20new%20workspace.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2010%2F30%2000%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jeff%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-1835416%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 29 October 2020 22:48 UTC

Our logs indicate the incident started on 10/29, 21:30 UTC and that during the 1 hour that it took to resolve the issue no customers experienced an issue trying to create a new workspace and receiving "internal server error" as a result.
  • Root Cause: The failure was due to a DNS limit being reached in China region.
  • Incident Timeline: 1 Hours & 0 minutes - 10/29, 21:30 UTC through 10/29, 22:30 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jeff

Initial Update: Thursday, 29 October 2020 22:04 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers in the China region may experience an "internal server error" when trying to create a new workspace.
  • Next Update: Before 10/30 00:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jeff