%3CLINGO-SUB%20id%3D%22lingo-sub-742470%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2007%2F08%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-742470%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%20Monday%2C%2008%20July%202019%2016%3A07%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2007%2F08%2C%2015%3A55%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2007%2F08%2C%2011%3A55%20UTC%20and%20that%20during%20the%204%20hours%20that%20it%20took%20to%20resolve%20the%20issue%2015%25%20of%20customers%20using%20Log%20Analytics%20would%20have%20experienced%20data%20access%20issues%20in%20East%20US%20region%20including%20issues%20accessing%20Log%20Search%20Alerts%20and%20Log%20Search%20queries%20via%20the%20Azure%20Portal..%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20with%20one%20of%20our%20backend%20services%20which%20went%20in%20to%20unhealthy%20state.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%204%20Hours%20-%2007%2F08%2C%2011%3A55%20UTC%20through%2007%2F08%2C%2015%3A55%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-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%20Monday%2C%2008%20July%202019%2015%3A38%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%20using%20Log%20Analytics%20in%20East%20US%20may%20experience%20data%20access%20issues%20including%20issues%20accessing%20Log%20Search%20Alerts%20and%20Log%20Search%20queries%20via%20the%20Azure%20Portal..%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F08%20~11%3A55%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%2F08%2018%3A00%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%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2008%20July%202019%2013%3A21%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20data%20access%20issue%20in%20east%20US%20region%20as%20our%20dependent%20backend%20service%20is%20having%20issues.%20Some%20customers%20may%20also%20see%20query%20degradation%20and%20face%20issues%20with%20log%20search%20alerts.%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%2F08%2015%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Rama%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-742470%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Monday, 08 July 2019 16:07 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/08, 15:55 UTC. Our logs show the incident started on 07/08, 11:55 UTC and that during the 4 hours that it took to resolve the issue 15% of customers using Log Analytics would have experienced data access issues in East US region including issues accessing Log Search Alerts and Log Search queries via the Azure Portal..
  • Root Cause: The failure was due to issues with one of our backend services which went in to unhealthy state.
  • Incident Timeline: 4 Hours - 07/08, 11:55 UTC through 07/08, 15:55 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Rama

Update: Monday, 08 July 2019 15:38 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers using Log Analytics in East US may experience data access issues including issues accessing Log Search Alerts and Log Search queries via the Azure Portal.. We are working to establish the start time for the issue, initial findings indicate that the problem began at 07/08 ~11:55 UTC. We currently have no estimate for resolution.
  • Work Around: None
  • Next Update: Before 07/08 18:00 UTC
-Rama

Initial Update: Monday, 08 July 2019 13:21 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue in east US region as our dependent backend service is having issues. Some customers may also see query degradation and face issues with log search alerts.
  • Work Around: none
  • Next Update: Before 07/08 15:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Rama