Home
%3CLINGO-SUB%20id%3D%22lingo-sub-381664%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2003%2F21%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-381664%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%20Thursday%2C%2021%20March%202019%2022%3A26%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%203%2F21%2C%2022%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%203%2F21%2C%2021%3A15%20UTC%20and%20that%20during%20the%201%20hour%20that%20it%20took%20to%20resolve%20the%20issue%2012%25%20of%20customers%20experienced%20an%20inability%20to%20query%20data%20in%20China%20-%20Mooncake%20region.%3CBR%20%2F%3E%3CUL%3E%0A%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20invalid%20replicated%20configuration%3C%2FLI%3E%0A%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20-%20%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23000000%3B%20font-family%3A%20'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E3%2F21%2C%2021%3A15%20UTC%3C%2FSPAN%3E%20through%20%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23000000%3B%20font-family%3A%20'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E3%2F21%2C%2022%3A15%20UTC%3C%2FSPAN%3E%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-Jeff%20Miller%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%3EUpdate%3C%2FU%3E%3A%20Thursday%2C%2021%20March%202019%2022%3A02%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20An%20invalid%20configuration%20replicated%20to%20the%20region%20which%20was%20impacting%20customer%20ability%20to%20query%20data.%20To%20address%20this%20issue%20we%20are%20reverting%20the%20configuration%20change.%26nbsp%3B%3CBR%20%2F%3E%3CUL%3E%0A%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%20at%20this%20time%3C%2FLI%3E%0A%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2003%2F22%2000%3A30%20UTC%3C%2FLI%3E%0A%3C%2FUL%3E-Jeff%20Miller%3C%2FDIV%3E%0A%3CHR%20%2F%3E%0A%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%3E%26nbsp%3B%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-381664%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 21 March 2019 22:26 UTC

We've confirmed that all systems are back to normal with no customer impact as of 3/21, 22:15 UTC. Our logs show the incident started on 3/21, 21:15 UTC and that during the 1 hour that it took to resolve the issue 12% of customers experienced an inability to query data in China - Mooncake region.
  • Root Cause: The failure was due to an invalid replicated configuration
  • Incident Timeline: 1 Hour - 3/21, 21:15 UTC through 3/21, 22:15 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jeff Miller

Update: Thursday, 21 March 2019 22:02 UTC

Root cause has been isolated to An invalid configuration replicated to the region which was impacting customer ability to query data. To address this issue we are reverting the configuration change. 
  • Work Around: None at this time
  • Next Update: Before 03/22 00:30 UTC
-Jeff Miller