Home
%3CLINGO-SUB%20id%3D%22lingo-sub-782814%22%20slang%3D%22en-US%22%3EExperiencing%20intermittent%20data%20gaps%20issue%20for%20Log%20Analytics%20-%2008%2F01%20-%20Investigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-782814%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%3EUpdate%3C%2FU%3E%3A%20Thursday%2C%2001%20August%202019%2007%3A37%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Customers%20using%20Solution%20Targeting%20feature%20within%20Log%20Analytics%20in%20East%20US%20might%20continue%20to%20see%20intermittent%20data%20gaps%20related%20to%20solution%20specific%20data.%20Service%20is%20back%20to%20normal%20in%20Central%20Canada%20region%20as%20of%26nbsp%3B%2008%2F01%2004%3A00%20UTC.%26nbsp%3B%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%2008%2F01%2010%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Naresh%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%20Thursday%2C%2001%20August%202019%2007%3A20%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Customers%20using%20Solution%20Targeting%20feature%20within%20Log%20Analytics%20in%20East%20US%20and%20Central%20Canada%20regions%20might%20continue%20to%20see%20intermittent%20data%20gaps%20related%20to%20solution%20specific%20data.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F31%20~19%3A20%20UTC.%26nbsp%3B%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%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%2008%2F01%2009%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Naresh%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%20Thursday%2C%2001%20August%202019%2004%3A54%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.%20Customers%20using%20Solution%20Targeting%20feature%20within%20Log%20Analytics%20in%20East%20US%20and%20Central%20Canada%20regions%20might%20continue%20to%20see%20intermittent%20data%20gaps%20related%20to%20solution%20specific%20data.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2007%2F27%20~06%3A00%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%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%2008%2F01%2007%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Naresh%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22%22%3E%3CDIV%20style%3D%22%22%3E%3CDIV%20style%3D%22%22%3E%3CP%20class%3D%22MsoNormal%22%20style%3D%22margin-bottom%3A%207.5pt%3B%20background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3E%3CU%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3EUpdate%3C%2FSPAN%3E%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3E%3A%20Thursday%2C%2001%20August%202019%2003%3A17%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.%26nbsp%3BCustomers%20using%20Solution%20Targeting%20feature%20within%20Log%20Analytics%20in%20East%20US%20and%20Central%20Canada%20regions%20might%20continue%20to%20see%20intermittent%20data%20gaps%20related%20to%20solution%20specific%20data.%26nbsp%3BWe%20currently%20have%20no%20estimate%20for%20resolution.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%20class%3D%22MsoNormal%22%20style%3D%22margin-bottom%3A%207.5pt%3B%20background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Finsights%2Fsolution-targeting%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-monitor%2Finsights%2Fsolution-targeting%26nbsp%3B%3C%2FA%3E%3CBR%20%2F%3E%20%3C!--%5Bif%20!supportLineBreakNewLine%5D--%3E%3CBR%20%2F%3E%20%3C!--%5Bendif%5D--%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CUL%20type%3D%22disc%22%3E%0A%20%3CLI%20class%3D%22MsoNormal%22%20style%3D%22background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3E%3CU%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3Bfont-family%3A%22%3EWork%20Around%3C%2FSPAN%3E%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3B%0A%20%20%20%20%20font-family%3A%22%20helvetica%3D%22%22%3E%3A%20none%3CP%3E%3C%2FP%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%20%3CLI%20class%3D%22MsoNormal%22%20style%3D%22background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3E%3CU%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3Bfont-family%3A%22%3ENext%20Update%3C%2FSPAN%3E%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A10.5pt%3B%0A%20%20%20%20%20font-family%3A%22%20helvetica%3D%22%22%3E%3A%20Before%2008%2F01%2005%3A30%20UTC%3CP%3E%3C%2FP%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%3CP%20class%3D%22MsoNormal%22%20style%3D%22margin-bottom%3A%207.5pt%3B%20background-image%3A%20initial%3B%20background-position%3A%20initial%3B%20background-size%3A%20initial%3B%20background-repeat%3A%20initial%3B%20background-attachment%3A%20initial%3B%20background-origin%3A%20initial%3B%20background-clip%3A%20initial%3B%22%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3E-Sindhu%26nbsp%3B%20%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%20class%3D%22MsoNormal%22%3E%3C%2FP%3E%3CP%20class%3D%22MsoNormal%22%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3C%2FDIV%3E%3CHR%20style%3D%22font-size%3A%2014px%3B%20border-top-color%3A%20lightgray%3B%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A%2014px%3B%22%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%2001%20August%202019%2001%3A29%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%26nbsp%3B%3CSPAN%20style%3D%22font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3ECustomers%20using%20Solution%20Targeting%20feature%20within%20Log%20Analytics%20in%20East%20US%20and%20Central%20Canada%20regions%20might%20see%20intermittent%20data%20gaps%20related%20to%20solution%20specific%20data%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-size%3A%2010.5pt%3B%20font-family%3A%20Helvetica%2C%20sans-serif%3B%22%3E.%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3E%3CBR%20%2F%3E%3C%2FU%3E%3C%2FDIV%3E%3CUL%3E%3CLI%20style%3D%22font-size%3A%2014px%3B%22%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2008%2F01%2003%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.-Sindhu%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%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-782814%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Thursday, 01 August 2019 16:36 UTC

We've confirmed that all systems are back to normal as of 08/01, 14:45 UTC. Our logs show the incident started on 07/31, 19:20 UTC and that during the 19 hours & 05 minutes that it took to resolve the issue some customers workspaces would not have received correct updates for solution targeting feature. Service is fully backup and processing the backlog. We estimate next 4-6 hours for backlog to be completely processed and some customers may continue to see residual impact until the backlog is fully caught up.

  • Root Cause: The failure was due to a scheduling service within Log Analytics feature which experienced performance degradation.
  • Lessons Learned: We will be performing full postmortem of this issue and will be taking up steps to alleviate any further reliability issues.
  • Incident Timeline: 19 Hours & 05 minutes - 07/31, 19:20 UTC through 08/01, 14:45 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Naresh

Final Update: Thursday, 01 August 2019 16:28 UTC

We've confirmed that all systems are back to normal as of 08/01, 14:45 UTC. Our logs show the incident started on 07/31, 19:20 UTC and that during the 19 hours & 05 minutes that it took to resolve the issue some customers workspaces would not have received correct updates for solution targeting feature. Service if fully backup and processing the backlog. We estimate next 4-6 hours for backlog to be completely processed and some customers may continue to see residual impact until the backlog is fully caught up.
  • Root Cause: The failure was due to a scheduling service within Log Analytics feature which experienced performance degradation.
  • Lessons Learned: We will be performing full postmortem of this issue and will be taking up steps to alleviate any further reliability issues.
  • Incident Timeline: 19 Hours & 05 minutes - 07/31, 19:20 UTC through 08/01, 14:45 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Naresh

Final Update: Thursday, 01 August 2019 16:10 UTC

We've confirmed that all systems are back to normal as of 08/01, 02:46 UTC. Our logs show the incident started on 07/31, 19:20 UTC and that during the 7 hours & 16 minutes that it took to resolve the issue some customers workspaces would not have received correct updates for solution targeting feature. Service if fully backup and processing the backlog. We estimate next 4-6 hours for backlog to be completely processed and some customers may continue to see residual impact until the backlog is fully caught up.
  • Root Cause: The failure was due to a scheduling service within Log Analytics feature which experienced performance degradation.
  • Lessons Learned: We will be performing full postmortem of this issue and will be taking up steps to alleviate any further reliability issues.
  • Incident Timeline: 7 Hours & 16 minutes - 07/31, 19:20 UTC through 08/01, 02:46 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Naresh

Update: Thursday, 01 August 2019 14:52 UTC

Root cause has been isolated to Solution Targeting feature which was impacting Log Analytics. To address this issue we rolled back to previous version of service. Solution Targeting feature is now working as expected. Some customers may experience intermittent data gaps related to solution specific data and we estimate 2hours before all data gaps is addressed.

  • Work Around: Rollback to previous version of the back-end service.
  • Next Update: Before 08/01 17:00 UTC
-Naresh

Update: Thursday, 01 August 2019 12:48 UTC

We continue to investigate issues within Log Analytics. Customers using Solution Targeting feature within Log Analytics in East US might continue to see intermittent data gaps related to solution specific data. We are working to establish the start time for the issue, initial findings indicate that the problem began at 07/31 ~19:20 UTC. 

  • Work Around: None
  • Next Update: Before 08/01 15:00 UTC
-Naresh

Update: Thursday, 01 August 2019 10:18 UTC

We continue to investigate issues within Log Analytics. Customers using Solution Targeting feature within Log Analytics in East US might continue to see intermittent data gaps related to solution specific data. We are working to establish the start time for the issue, initial findings indicate that the problem began at 07/31 ~19:20 UTC. 

  • Work Around: None
  • Next Update: Before 08/01 12:30 UTC
-Naresh

Update: Thursday, 01 August 2019 07:37 UTC

We continue to investigate issues within Log Analytics. Customers using Solution Targeting feature within Log Analytics in East US might continue to see intermittent data gaps related to solution specific data. Service is back to normal in Central Canada region as of  08/01 04:00 UTC. 
  • Work Around: None
  • Next Update: Before 08/01 10:00 UTC
-Naresh

Update: Thursday, 01 August 2019 07:20 UTC

We continue to investigate issues within Log Analytics. Customers using Solution Targeting feature within Log Analytics in East US and Central Canada regions might continue to see intermittent data gaps related to solution specific data. We are working to establish the start time for the issue, initial findings indicate that the problem began at 07/31 ~19:20 UTC. 

  • Work Around: None
  • Next Update: Before 08/01 09:30 UTC
-Naresh

Update: Thursday, 01 August 2019 04:54 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Customers using Solution Targeting feature within Log Analytics in East US and Central Canada regions might continue to see intermittent data gaps related to solution specific data. We are working to establish the start time for the issue, initial findings indicate that the problem began at 07/27 ~06:00 UTC. We currently have no estimate for resolution.

  • Work Around: none
  • Next Update: Before 08/01 07:00 UTC
-Naresh

Update: Thursday, 01 August 2019 03:17 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Customers using Solution Targeting feature within Log Analytics in East US and Central Canada regions might continue to see intermittent data gaps related to solution specific data. We currently have no estimate for resolution.

https://docs.microsoft.com/en-us/azure/azure-monitor/insights/solution-targeting 

  • Work Around: none

  • Next Update: Before 08/01 05:30 UTC

-Sindhu   

 


Initial Update: Thursday, 01 August 2019 01:29 UTC

We are aware of issues within Log Analytics and are actively investigating. Customers using Solution Targeting feature within Log Analytics in East US and Central Canada regions might see intermittent data gaps related to solution specific data.

  • Next Update: Before 08/01 03:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Sindhu