Home
%3CLINGO-SUB%20id%3D%22lingo-sub-755937%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2007%2F16%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-755937%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%20Tuesday%2C%2016%20July%202019%2017%3A55%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%207%2F16%2C%2015%3A45%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%207%2F15%2C%2014%3A40%20UTC%20and%20that%20during%20the%20of%20the%20incident%20retrying%20might%20have%20worked.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20Yet%20to%20be%20determined.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2023%20Hours%20%26amp%3B%205%20minutes%20-%207%2F15%2C%2014%3A40%20UTC%20through%207%2F16%2C%2015%3A45%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-Dharmendra%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%3EUpdate%3C%2FU%3E%3A%20Tuesday%2C%2016%20July%202019%2014%3A38%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20the%20same%20as%20described%20below.%20To%20address%20this%20issue%20we%20have%20carried%20out%20series%20of%20mitigation%20steps%20which%20has%20given%20us%20partial%20results.We%20are%20still%20working%20through%20mitigation%20plan%20to%20get%20the%20impacted%20cluster%20in%20South%20East%20Asia%20region%20back%20to%20normal%20operating%20levels.%20Some%20customers%20from%20Southeast%20asia%20region%20may%20experience%20query%20failures%20which%20accessing%20Data.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2007%2F16%2019%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Durga%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%3EUpdate%3C%2FU%3E%3A%20Tuesday%2C%2016%20July%202019%2010%3A09%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20configuration%20change%20which%20inadvertently%20caused%20performance%20degradation%20to%202%20of%20the%20impacted%20backend%20clusters%26nbsp%3B%20.%20To%20address%20this%20issue%20we%20have%20rolled%20back%20the%20change%20and%20also%20performed%20additional%20mitigation.%20Southeast%20Australia%20region%20is%20now%20working%20as%20expected.%20Some%20customers%20may%20still%20experience%20query%20and%20data%20access%20issues%20with%20Southeast%20Asia%20region%20as%20we%20are%20working%20on%20mitigation%20in%20this%20region%20to%20stabilize%20impacted%20backend%20cluster.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2007%2F16%2014%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Durga%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%3EUpdate%3C%2FU%3E%3A%20Tuesday%2C%2016%20July%202019%2007%3A08%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Very%20small%20subset%20of%20customers%20continue%20to%20experience%20data%20access%20issue%26nbsp%3Busing%20Log%20Analytics%20in%20Southeast%20Asia%20and%20Southeast%20Australia%20region.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F15%20~21%3A51%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2007%2F16%2010%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Rama%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%3EUpdate%3C%2FU%3E%3A%20Tuesday%2C%2016%20July%202019%2002%3A52%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%22%200px%3D%22%22%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20may%20continue%20to%20experience%3C%2FSPAN%3E%3CSPAN%20style%3D%22background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20box-sizing%3A%20border-box%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20display%3A%20inline%3B%20float%3A%20none%3B%20font-family%3A%20%22%200px%3D%22%22%3Eissue%20using%20Log%20Analytics%20in%20Southeast%20Asia%20and%20Australia%20Southeast.%3C%2FSPAN%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%22%200px%3D%22%22%3E%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue.%20Initial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F15%2021%3A51%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3C%2FSPAN%3E%3CBR%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%22%200px%3D%22%22%20%2F%3E%3CUL%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%22%200px%3D%22%22%3E%3CLI%20style%3D%22box-sizing%3A%20border-box%3B%22%3E%3CU%20style%3D%22box-sizing%3A%20border-box%3B%22%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3C%2FUL%3E%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2007%2F16%2005%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Dharmendra%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%3EUpdate%3C%2FU%3E%3A%20Tuesday%2C%2016%20July%202019%2001%3A18%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20may%20continue%20to%20experience%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%22%200px%3D%22%22%3Eissue%20using%20Log%20Analytics%20in%20Southeast%20Asia%20and%20Australia%20Southeast.%3C%2FSPAN%3E%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue.%20Initial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F15%2021%3A51%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2007%2F16%2002%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Dharmendra%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%20Tuesday%2C%2016%20July%202019%2000%3A01%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20issue%20using%20Log%20Analytics%20in%20Southeast%20Asia%20and%20Australia%20Southeast%20.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%20at%20the%20time%20of%20incident%20%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2007%2F16%2001%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Dharmendra%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-755937%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 16 July 2019 17:55 UTC

We've confirmed that all systems are back to normal with no customer impact as of 7/16, 15:45 UTC. Our logs show the incident started on 7/15, 14:40 UTC and that during the of the incident retrying might have worked.
  • Root Cause: Yet to be determined.
  • Incident Timeline: 23 Hours & 5 minutes - 7/15, 14:40 UTC through 7/16, 15:45 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Dharmendra

Update: Tuesday, 16 July 2019 14:38 UTC

Root cause has been isolated to the same as described below. To address this issue we have carried out series of mitigation steps which has given us partial results.We are still working through mitigation plan to get the impacted cluster in South East Asia region back to normal operating levels. Some customers from Southeast asia region may experience query failures which accessing Data.
  • Work Around: None
  • Next Update: Before 07/16 19:00 UTC
-Durga

Update: Tuesday, 16 July 2019 10:09 UTC

Root cause has been isolated to configuration change which inadvertently caused performance degradation to 2 of the impacted backend clusters  . To address this issue we have rolled back the change and also performed additional mitigation. Southeast Australia region is now working as expected. Some customers may still experience query and data access issues with Southeast Asia region as we are working on mitigation in this region to stabilize impacted backend cluster.
  • Work Around: None
  • Next Update: Before 07/16 14:30 UTC
-Durga

Update: Tuesday, 16 July 2019 07:08 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Very small subset of customers continue to experience data access issue using Log Analytics in Southeast Asia and Southeast Australia region. We are working to establish the start time for the issue, initial findings indicate that the problem began at 07/15 ~21:51 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 07/16 10:30 UTC
-Rama

Update: Tuesday, 16 July 2019 02:52 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers may continue to experience issue using Log Analytics in Southeast Asia and Australia Southeast. We are working to establish the start time for the issue. Initial findings indicate that the problem began at 07/15 21:51 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 07/16 05:00 UTC
-Dharmendra

Update: Tuesday, 16 July 2019 01:18 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers may continue to experience issue using Log Analytics in Southeast Asia and Australia Southeast. We are working to establish the start time for the issue. Initial findings indicate that the problem began at 07/15 21:51 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 07/16 02:30 UTC
-Dharmendra

Initial Update: Tuesday, 16 July 2019 00:01 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issue using Log Analytics in Southeast Asia and Australia Southeast .
  • Work Around: None at the time of incident  
  • Next Update: Before 07/16 01:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Dharmendra