Experiencing Data Latency for Log Analytics - 06/20 - Resolved

Published Jun 20 2022 01:50 PM 4,667 Views
Final Update: Thursday, 23 June 2022 19:27 UTC

We've confirmed that all systems are back to normal with no customer impact as of 06/23, 17:00 UTC. Our logs show the incident started on 06/20, 16:00 UTC and that during the duration of incident hours that it took to resolve the issue most of customers in West Europe and some customer in South UK using Azure Log Analytics or Azure Sentinel who may have experienced issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel. Due to the impact to Log Analytics, customers using Azure Automation to delete / link Automation Accounts to workspaces would have been impacted. Customers using Azure Automation for Update Management solution may have seen their machines in a 'Not Assessed' state and Automation account not linked to Log Analytics. Customers using Automation for Change Tracking solution may not have seen their data updated in Log Analytics workspaces.
  • Root Cause: The failure was due to a backend service that Azure Log Analytics and Azure Sentinel utilizes became unhealthy due to a large volume of incoming requests. This was caused by the service auto scaling down resulting in a backlog of retries. During the process of working through the retry backlog, a subscription quota was reached, and the process was unable to get through this backlog.
  • Mitigation: After various mitigation workstream attempts, we have mitigated this issue which included performing a rollback to the last known healthy state, applying a scale out operation, and draining out backlog requests. 
  • Incident Timeline: 06/20, 16:00 UTC through 06/23, 17:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service, and we sincerely apologize for any impact this incident caused.

-Arish Balasubramani

Update: Thursday, 23 June 2022 13:17 UTC

Root cause has been isolated to high load on backend component which was impacting Log Analytics. To address this issue, we have rolled out configuration fix, Paused and restarted the responsible backend services along with scaling out backend services to catch up with latency to mitigate the issue. We have applied a series of mitigation steps and we are continuing to monitor the service health to validate mitigation in West Europe. Additional engineering teams are being engaged to verify if additional mitigation workstreams are needed and issue is mitigated for UK South. The next update will be provided in 4 hours or as events warrant. Some customers may continue to experience issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel.

Due to the impact to Log Analytics, customers using Azure Automation to delete/link automation accounts to workspaces will be impacted. Customers using Azure Automation for update management solution may see their machines in a 'Not Assessed' state and automation account not linked to Log Analytics. Customers using automation for change tracking solution may not see their data updated in Log Analytics Workspace.
We have entered the final phase of recovery where most data types have been recovered and customers will see signs of recovery. We are continuing to clear a backlog for some data types like IIS Logs and Custom Logs. Customers querying these data types may see some latency where query results may not reflect latest information. We are continuing to clear the backlog load for these data types. The next update will be provided in 4 hours or as events warrant.
  • Work Around: None
  • Next Update: Before 06/23 17:30 UTC
-Deepika

Update: Thursday, 23 June 2022 07:12 UTC

Root cause has been isolated to high load on backend component which was impacting Log Analytics. To address this issue, we have rolled out configuration fix, Paused and restarted the responsible backend services along with scaling out backend services to catch up with latency to mitigate the issue. We have applied a series of mitigation steps and we are continuing to monitor the service health to validate mitigation in West Europe. Additional engineering teams are being engaged to verify if additional mitigation workstreams are needed and issue is mitigated for UK South. The next update will be provided in 6 hours or as events warrant. Some customers may continue to experience issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel.

Due to the impact to Log Analytics, customers using Azure Automation to delete/link automation accounts to workspaces will be impacted. Customers using Azure Automation for update management solution may see their machines in a 'Not Assessed' state and automation account not linked to Log Analytics. Customers using automation for change tracking solution may not see their data updated in Log Analytics Workspace.

As our mitigation steps were successfully applied and backend services returning healthy. We are currently in the process of catching up with ingestion backlogs.

We have completed the recovery for most data types. We expect to finish recovering for some of the remaining data types by 12:30 UTC on 23 Jun 2022.

  • Work Around: None
  • Next Update: Before 06/23 19:30 UTC
-Anmol

Update: Wednesday, 22 June 2022 22:47 UTC

Root cause has been isolated to high load on backend component which was impacting Log Analytics. To address this issue, we have rolled out configuration fix, Paused and restarted the responsible backend services along with scaling out backend services to catch up with latency to mitigate the issue. We have applied a series of mitigation steps and we are continuing to monitor the service health to validate mitigation in West Europe. Additional engineering teams are being engaged to verify if additional mitigation workstreams are needed and issue is mitigated for UK South. The next update will be provided in 6 hours or as events warrant. Some customers may continue to experience issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel.

Due to the impact to Log Analytics, customers using Azure Automation to delete/link automation accounts to workspaces will be impacted. Customers using Azure Automation for update management solution may see their machines in a 'Not Assessed' state and automation account not linked to Log Analytics. Customers using automation for change tracking solution may not see their data updated in Log Analytics Workspace.

As our mitigation steps were successfully applied and backend services returning healthy. We are currently in the process of catching up with ingestion backlogs

  • Work Around:
  • Next Update: Before 06/23 05:00 UTC
-Arish Balasubramani

Update: Wednesday, 22 June 2022 11:34 UTC

Root cause has been isolated to high load on backend component which was impacting Log Analytics. To address this issue, we have rolled out configuration fix, Paused and restarted the responsible backend services along with scaling out backend services to catch up with latency to mitigate the issue. We have applied a series of mitigation steps and we are continuing to monitor the service health to validate mitigation in West Europe. Additional engineering teams are being engaged to verify if additional mitigation workstreams are needed and issue is mitigated for UK South. The next update will be provided in 6 hours or as events warrant. Some customers may continue to experience issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel.

Due to the impact to Log Analytics, customers using Azure Automation to delete/link automation accounts to workspaces will be impacted. Customers using Azure Automation for update management solution may see their machines in a 'Not Assessed' state and automation account not linked to Log Analytics. Customers using automation for change tracking solution may not see their data updated in Log Analytics Workspace.
  • Work Around: None
  • Next Update: Before 06/22 18:00 UTC
-Sai Kumar

Update: Wednesday, 22 June 2022 06:29 UTC

Root cause has been isolated to high load on backend component which was impacting Log Analytics. To address this issue, we have rolled out configuration fix, Paused and restarted the responsible backend services along with scaling out backend services to catch up with latency to mitigate the issue. We are currently monitoring service health to confirm mitigation as we see signs of recovery for West Europe. And mitigation steps are in progress for UK South. The next update will be provided in 5 hours or as events warrant. Some customers may continue to experience issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel.
  • Work Around: None
  • Next Update: Before 06/22 11:30 UTC
-Deepika

Update: Wednesday, 22 June 2022 02:55 UTC

Root cause has been isolated to high load on backend component which was impacting Log Analytics. To address this issue, we have rolled out configuration fix, Paused and restarted the responsible backend services along with scaling out backend services to catch up with latency to mitigate the issue. We are currently monitoring service health to confirm mitigation as we see signs of recovery for West Europe. And mitigation steps are in progress for UK South. The next update will be provided in 3 hours or as events warrant. Some customers may continue to experience issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel.
  • Work Around: NA
  • Next Update: Before 06/22 06:00 UTC
-Arish Balasubramani

Update: Tuesday, 21 June 2022 21:56 UTC

Root cause has been isolated to high load on backend component which was impacting Log Analytics. To address this issue, we are rolling out the fix that help with the load, paused a responsible backend service from creating more load in order to mitigate the issue. The next update will be provided in 3 hours or as events warrant. Some customers may continue to experience issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel.
  • Work Around: NA
  • Next Update: Before 06/22 02:00 UTC
-Arish Balasubramani

Update: Tuesday, 21 June 2022 15:10 UTC

Root cause has been isolated to high load on backend component which was impacting Log Analytics. To address this issue we are rolling out the fix that help with the load in order to mitigate the issue. The next update will be provided in 3 hours or as events warrant. Some customers may continue to experience issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel.
  • Work Around: NA
  • Next Update: Before 06/21 18:30 UTC
-Deepika

Update: Tuesday, 21 June 2022 09:02 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers may continue to experience issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel. Our initial findings indicate that the problem began at 06/20 16:00 UTC. We currently have no estimate for resolution, Adding Cores Capacity to WEU allowing the service to scale out did not help.
  • Work Around: NA
  • Next Update: Before 06/21 14:30 UTC
-Deepika

Update: Tuesday, 21 June 2022 05:25 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers may continue to experience issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel. Our initial findings indicate that the problem began at 06/20 16:00 UTC. We currently have no estimate for resolution, Adding Cores Capacity to WEU allowing the service to scale out did not help.
  • Work Around: NA
  • Next Update: Before 06/21 08:30 UTC
-Deepika

Update: Monday, 20 June 2022 20:40 UTC

We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers may continue to experience issues with data access, missed or delayed log search alerts, data gaps and data latency and issues with Azure Sentinel. Our initial findings indicate that the problem began at 06/20 17:15 PM UTC. We currently have no estimate for resolution, Adding Cores Capacity to WEU allowing the service to scale out did not help.
  • Work Around: NA
  • Next Update: Before 06/20 23:00 UTC
-Arish Balasubramani

1 Comment
%3CLINGO-SUB%20id%3D%22lingo-sub-3536865%22%20slang%3D%22en-US%22%3ERe%3A%20Experiencing%20Data%20Latency%20for%20Log%20Analytics%20-%2006%2F20%20-%20Mitigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3536865%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3CBR%20%2F%3E%3CBR%20%2F%3Eas%20per%20described%20instruction%20i%20follow%20the%20steps%20but%20the%20issue%20is%20not%20resolved%20till%20yet%20not%20able%20to%20check%20the%20outbound%20logs%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3530728%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20for%20Log%20Analytics%20-%2006%2F20%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3530728%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EFinal%20Update%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3A%20Thursday%2C%2023%20June%202022%2019%3A27%20UTC%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2006%2F23%2C%2017%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2006%2F20%2C%2016%3A00%20UTC%20and%20that%20during%20the%20duration%20of%20incident%20hours%20that%20it%20took%20to%20resolve%20the%20issue%20most%20of%20customers%20in%20West%20Europe%20and%20some%20customer%20in%20South%20UK%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%20color%3A%20rgb(36%2C%2036%2C%2036)%3B%20font-family%3A%20-apple-system%2C%20BlinkMacSystemFont%2C%20%26quot%3BSegoe%20UI%26quot%3B%2C%20system-ui%2C%20%26quot%3BApple%20Color%20Emoji%26quot%3B%2C%20%26quot%3BSegoe%20UI%20Emoji%26quot%3B%2C%20%26quot%3BSegoe%20UI%20Web%26quot%3B%2C%20sans-serif%3B%22%3Eusing%20Azure%20Log%20Analytics%20or%20Azure%20Sentinel%20who%20may%20have%20experienced%20issues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%20Sentinel.%26nbsp%3B%3C%2FSPAN%3E%3CFONT%20color%3D%22%23242424%22%20face%3D%22-apple-system%2C%20BlinkMacSystemFont%2C%20Segoe%20UI%2C%20system-ui%2C%20Apple%20Color%20Emoji%2C%20Segoe%20UI%20Emoji%2C%20Segoe%20UI%20Web%2C%20sans-serif%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3EDue%20to%20the%20impact%20to%20Log%20Analytics%2C%20customers%20using%20Azure%20Automation%20to%20delete%20%2F%20link%20Automation%20Accounts%20to%20workspaces%20would%20have%20been%20impacted.%20Customers%20using%20Azure%20Automation%20for%20Update%20Management%20solution%20may%20have%20seen%20their%20machines%20in%20a%20'Not%20Assessed'%20state%20and%20Automation%20account%20not%20linked%20to%20Log%20Analytics.%20Customers%20using%20Automation%20for%20Change%20Tracking%26nbsp%3Bsolution%20may%20not%20have%20seen%20their%20data%20updated%20in%20Log%20Analytics%20workspaces.%3C%2FSPAN%3E%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20backend%20service%20that%20Azure%20Log%20Analytics%20and%20Azure%20Sentinel%20utilizes%20became%20unhealthy%20due%20to%20a%20large%20volume%20of%20incoming%20requests.%20This%20was%20caused%20by%20the%20service%20auto%20scaling%20down%20resulting%20in%20a%20backlog%20of%20retries.%20During%20the%20process%20of%20working%20through%20the%20retry%20backlog%2C%20a%20subscription%20quota%20was%20reached%2C%20and%20the%20process%20was%20unable%20to%20get%20through%20this%20backlog.%3C%2FLI%3E%3CLI%3E%3CU%3EMitigation%3C%2FU%3E%3A%20After%20various%20mitigation%20workstream%20attempts%2C%20we%20have%20mitigated%20this%20issue%20which%20included%20performing%20a%20rollback%20to%20the%20last%20known%20healthy%20state%2C%20applying%20a%20scale%20out%20operation%2C%20and%20draining%20out%20backlog%20requests.%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2006%2F20%2C%2016%3A00%20UTC%26nbsp%3Bthrough%2006%2F23%2C%2017%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%20as%20a%20critical%20service%2C%20and%20we%26nbsp%3B%3CSPAN%20style%3D%22color%3A%20rgb(36%2C%2036%2C%2036)%3B%20font-family%3A%20-apple-system%2C%20BlinkMacSystemFont%2C%20%26quot%3BSegoe%20UI%26quot%3B%2C%20system-ui%2C%20%26quot%3BApple%20Color%20Emoji%26quot%3B%2C%20%26quot%3BSegoe%20UI%20Emoji%26quot%3B%2C%20%26quot%3BSegoe%20UI%20Web%26quot%3B%2C%20sans-serif%3B%22%3Esincerely%20apologize%26nbsp%3B%3C%2FSPAN%3Efor%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Arish%20Balasubramani%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%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EUpdate%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3A%20Thursday%2C%2023%20June%202022%2013%3A17%20UTC%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3ERoot%20cause%20has%20been%20isolated%20to%20high%20load%20on%20backend%20component%20which%20was%20impacting%20Log%20Analytics.%20To%20address%20this%20issue%2C%20we%20have%20rolled%20out%20configuration%20fix%2C%20Paused%20and%20restarted%20the%20responsible%20backend%20services%20along%20with%20scaling%20out%20backend%20services%20to%20catch%20up%20with%20latency%20to%20mitigate%20the%20issue.%20We%20have%20applied%20a%20series%20of%20mitigation%20steps%20and%20we%20are%20continuing%20to%20monitor%20the%20service%20health%20to%20validate%20mitigation%20in%20West%20Europe.%20Additional%20engineering%20teams%20are%20being%20engaged%20to%20verify%20if%20additional%20mitigation%20workstreams%20are%20needed%20and%20issue%20is%20mitigated%20for%20UK%20South.%20The%20next%20update%20will%20be%20provided%20in%204%20hours%20or%20as%20events%20warrant.%20Some%20customers%20may%20continue%20to%20experience%20issues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%20Sentinel.%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3EDue%20to%20the%20impact%20to%20Log%20Analytics%2C%20customers%20using%20Azure%20Automation%20to%20delete%2Flink%20automation%20accounts%20to%20workspaces%20will%20be%20impacted.%20Customers%20using%20Azure%20Automation%20for%20update%20management%20solution%20may%20see%20their%20machines%20in%20a%20'Not%20Assessed'%20state%20and%20automation%20account%20not%20linked%20to%20Log%20Analytics.%20Customers%20using%20automation%20for%20change%20tracking%20solution%20may%20not%20see%20their%20data%20updated%20in%20Log%20Analytics%20Workspace.%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22white-space%3A%20pre%3B%20font-size%3A%2014px%3B%22%3E%20%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3EWe%20have%20entered%20the%20final%20phase%20of%20recovery%20where%20most%20data%20types%20have%20been%20recovered%20and%20customers%20will%20see%20signs%20of%20recovery.%20We%20are%20continuing%20to%20clear%20a%20backlog%20for%20some%20data%20types%20like%20IIS%20Logs%20and%20Custom%20Logs.%20Customers%20querying%20these%20data%20types%20may%20see%20some%20latency%20where%20query%20results%20may%20not%20reflect%20latest%20information.%20We%20are%20continuing%20to%20clear%20the%20backlog%20load%20for%20these%20data%20types.%20The%20next%20update%20will%20be%20provided%20in%204%20hours%20or%20as%20events%20warrant.%3C%2FSPAN%3E%3C%2FDIV%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F23%2017%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E-Deepika%3C%2FSPAN%3E%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%2023%20June%202022%2007%3A12%20UTC%3CBR%20%2F%3E%3C%2FDIV%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%3CBR%20%2F%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3ERoot%20cause%20has%20been%20isolated%20to%20high%20load%20on%20backend%20component%20which%20was%20impacting%20Log%20Analytics.%20To%20address%20this%20issue%2C%20we%20have%20rolled%20out%20configuration%20fix%2C%20Paused%20and%20restarted%20the%20responsible%20backend%20services%20along%20with%20scaling%20out%20backend%20services%20to%20catch%20up%20with%20latency%20to%20mitigate%20the%20issue.%20We%20have%20applied%20a%20series%20of%20mitigation%20steps%20and%20we%20are%20continuing%20to%20monitor%20the%20service%20health%20to%20validate%20mitigation%20in%20West%20Europe.%20Additional%20engineering%20teams%20are%20being%20engaged%20to%20verify%20if%20additional%20mitigation%20workstreams%20are%20needed%20and%20issue%20is%20mitigated%20for%20UK%20South.%20The%20next%20update%20will%20be%20provided%20in%206%20hours%20or%20as%20events%20warrant.%20Some%20customers%20may%20continue%20to%20experience%20issues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%20Sentinel.%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3EDue%20to%20the%20impact%20to%20Log%20Analytics%2C%20customers%20using%20Azure%20Automation%20to%20delete%2Flink%20automation%20accounts%20to%20workspaces%20will%20be%20impacted.%20Customers%20using%20Azure%20Automation%20for%20update%20management%20solution%20may%20see%20their%20machines%20in%20a%20'Not%20Assessed'%20state%20and%20automation%20account%20not%20linked%20to%20Log%20Analytics.%20Customers%20using%20automation%20for%20change%20tracking%20solution%20may%20not%20see%20their%20data%20updated%20in%20Log%20Analytics%20Workspace.%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3EAs%20our%20mitigation%20steps%20were%20successfully%20applied%20and%20backend%20services%20returning%20healthy.%20We%20are%20currently%20in%20the%20process%20of%20catching%20up%20with%20ingestion%20backlogs.%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3EWe%20have%20completed%20the%20recovery%20for%20most%20data%20types.%20We%20expect%20to%20finish%20recovering%20for%20some%20of%20the%20remaining%20data%20types%20by%2012%3A30%20UTC%20on%2023%20Jun%202022.%3C%2FSPAN%3E%3C%2FDIV%3E%3CBR%20%2F%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F23%2019%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E-Anmol%3C%2FSPAN%3E%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%3CU%3EUpdate%3C%2FU%3E%3A%20Wednesday%2C%2022%20June%202022%2022%3A47%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%3ERoot%20cause%20has%20been%20isolated%20to%20high%20load%20on%20backend%20component%20which%20was%20impacting%20Log%20Analytics.%20To%20address%20this%20issue%2C%20we%20have%20rolled%20out%20configuration%20fix%2C%20Paused%20and%20restarted%20the%20responsible%20backend%20services%20along%20with%20scaling%20out%20backend%20services%20to%20catch%20up%20with%20latency%20to%20mitigate%20the%20issue.%20We%20have%20applied%20a%20series%20of%20mitigation%20steps%20and%20we%20are%20continuing%20to%20monitor%20the%20service%20health%20to%20validate%20mitigation%20in%20West%20Europe.%20Additional%20engineering%20teams%20are%20being%20engaged%20to%20verify%20if%20additional%20mitigation%20workstreams%20are%20needed%20and%20issue%20is%20mitigated%20for%20UK%20South.%20The%20next%20update%20will%20be%20provided%20in%206%20hours%20or%20as%20events%20warrant.%20Some%20customers%20may%20continue%20to%20experience%20issues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%20Sentinel.%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%3EDue%20to%20the%20impact%20to%20Log%20Analytics%2C%20customers%20using%20Azure%20Automation%20to%20delete%2Flink%20automation%20accounts%20to%20workspaces%20will%20be%20impacted.%20Customers%20using%20Azure%20Automation%20for%20update%20management%20solution%20may%20see%20their%20machines%20in%20a%20'Not%20Assessed'%20state%20and%20automation%20account%20not%20linked%20to%20Log%20Analytics.%20Customers%20using%20automation%20for%20change%20tracking%20solution%20may%20not%20see%20their%20data%20updated%20in%20Log%20Analytics%20Workspace.%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%3EAs%20our%20mitigation%20steps%20were%20successfully%20applied%20and%20backend%20services%20returning%20healthy.%20We%20are%20currently%20in%20the%20process%20of%20catching%20up%20with%20ingestion%20backlogs%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%3CNONE%20or%3D%22%22%20details%3D%22%22%3E%3C%2FNONE%3E%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F23%2005%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Arish%20Balasubramani%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%20Wednesday%2C%2022%20June%202022%2011%3A34%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%3ERoot%20cause%20has%20been%20isolated%20to%20high%20load%20on%20backend%20component%20which%20was%20impacting%20Log%20Analytics.%20To%20address%20this%20issue%2C%20we%20have%20rolled%20out%20configuration%20fix%2C%20Paused%20and%20restarted%20the%20responsible%20backend%20services%20along%20with%20scaling%20out%20backend%20services%20to%20catch%20up%20with%20latency%20to%20mitigate%20the%20issue.%20We%20have%20applied%20a%20series%20of%20mitigation%20steps%20and%20we%20are%20continuing%20to%20monitor%20the%20service%20health%20to%20validate%20mitigation%20in%20West%20Europe.%20Additional%20engineering%20teams%20are%20being%20engaged%20to%20verify%20if%20additional%20mitigation%20workstreams%20are%20needed%20and%20issue%20is%20mitigated%20for%20UK%20South.%20The%20next%20update%20will%20be%20provided%20in%206%20hours%20or%20as%20events%20warrant.%20Some%20customers%20may%20continue%20to%20experience%20issues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%20Sentinel.%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%3EDue%20to%20the%20impact%20to%20Log%20Analytics%2C%20customers%20using%20Azure%20Automation%20to%20delete%2Flink%20automation%20accounts%20to%20workspaces%20will%20be%20impacted.%20Customers%20using%20Azure%20Automation%20for%20update%20management%20solution%20may%20see%20their%20machines%20in%20a%20'Not%20Assessed'%20state%20and%20automation%20account%20not%20linked%20to%20Log%20Analytics.%20Customers%20using%20automation%20for%20change%20tracking%20solution%20may%20not%20see%20their%20data%20updated%20in%20Log%20Analytics%20Workspace.%3C%2FDIV%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%2006%2F22%2018%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Sai%20Kumar%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%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EUpdate%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3A%20Wednesday%2C%2022%20June%202022%2006%3A29%20UTC%3C%2FSPAN%3E%3CBR%20%2F%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3ERoot%20cause%20has%20been%20isolated%20to%20high%20load%20on%20backend%20component%20which%20was%20impacting%20Log%20Analytics.%20To%20address%20this%20issue%2C%20we%20have%20rolled%20out%20configuration%20fix%2C%20Paused%20and%20restarted%20the%20responsible%20backend%20services%20along%20with%20scaling%20out%20backend%20services%20to%20catch%20up%20with%20latency%20to%20mitigate%20the%20issue.%20We%20are%20currently%20monitoring%20service%20health%20to%20confirm%20mitigation%20as%20we%20see%20signs%20of%20recovery%20for%20West%20Europe.%20And%20mitigation%20steps%20are%20in%20progress%20for%20UK%20South.%20The%20next%20update%20will%20be%20provided%20in%205%20hours%20or%20as%20events%20warrant.%20Some%20customers%20may%20continue%20to%20experience%20issues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%20Sentinel.%3C%2FSPAN%3E%3C%2FDIV%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F22%2011%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E-Deepika%3C%2FSPAN%3E%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%3E%3CU%3EUpdate%3C%2FU%3E%3A%20Wednesday%2C%2022%20June%202022%2002%3A55%20UTC%3C%2FDIV%3E%3CDIV%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20high%20load%20on%20backend%20component%20which%20was%20impacting%20Log%20Analytics.%20To%20address%20this%20issue%2C%20we%20have%20rolled%20out%20configuration%20fix%2C%20Paused%20and%20restarted%20the%20responsible%20backend%20services%20along%20with%20scaling%20out%20backend%20services%20to%20catch%20up%20with%20latency%20to%20mitigate%20the%20issue.%20We%20are%20currently%20monitoring%20service%20health%20to%20confirm%20mitigation%20as%20we%20see%20signs%20of%20recovery%20for%20West%20Europe.%20And%20mitigation%20steps%20are%20in%20progress%20for%20UK%20South.%20The%20next%20update%20will%20be%20provided%20in%203%20hours%20or%20as%20events%20warrant.%20Some%20customers%20may%20continue%20to%20experience%20issues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%20Sentinel.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20NA%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F22%2006%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Arish%20Balasubramani%3C%2FDIV%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%2021%20June%202022%2021%3A56%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20high%20load%20on%20backend%20component%20which%20was%20impacting%20Log%20Analytics.%20To%20address%20this%20issue%2C%20we%20are%20rolling%20out%20the%20fix%20that%20help%20with%20the%20load%2C%20paused%20a%20responsible%20backend%20service%20from%20creating%20more%20load%20in%20order%20to%20mitigate%20the%20issue.%20The%20next%20update%20will%20be%20provided%20in%203%20hours%20or%20as%20events%20warrant.%20Some%20customers%20may%20continue%20to%20experience%20issues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%20Sentinel.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20NA%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F22%2002%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Arish%20Balasubramani%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%2021%20June%202022%2015%3A10%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20high%20load%20on%20backend%20component%20which%20was%20impacting%20Log%20Analytics.%20To%20address%20this%20issue%20we%20are%20rolling%20out%20the%20fix%20that%20help%20with%20the%20load%20in%20order%20to%20mitigate%20the%20issue.%20The%20next%20update%20will%20be%20provided%20in%203%20hours%20or%20as%20events%20warrant.%20Some%20customers%20may%20continue%20to%20experience%20issues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%20Sentinel.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20NA%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F21%2018%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Deepika%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%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EUpdate%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3A%20Tuesday%2C%2021%20June%202022%2009%3A02%20UTC%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20may%20continue%20to%20experience%20issues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%20Sentinel.%20Our%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2006%2F20%2016%3A00%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution%2C%20Adding%20Cores%20Capacity%20to%20WEU%20allowing%20the%20service%20to%20scale%20out%20did%20not%20help.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20NA%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F21%2014%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E-Deepika%3C%2FSPAN%3E%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%2021%20June%202022%2005%3A25%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%20issues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%20Sentinel.%20Our%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2006%2F20%2016%3A00%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution%2C%20Adding%20Cores%20Capacity%20to%20WEU%20allowing%20the%20service%20to%20scale%20out%20did%20not%20help.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20NA%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F21%2008%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Deepika%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%22%22%3E%3CU%20style%3D%22font-size%3A%2014px%3B%22%3EUpdate%3C%2FU%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%3A%20Monday%2C%2020%20June%202022%2020%3A40%20UTC%3C%2FSPAN%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20may%20continue%20to%20experience%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%20color%3A%20rgb(37%2C%2036%2C%2035)%3B%20font-family%3A%20-apple-system%2C%20BlinkMacSystemFont%2C%20%22%20segoe%3D%22%22%20ui%3D%22%22%3Eissues%20with%20data%20access%2C%20missed%20or%20delayed%20log%20search%20alerts%2C%20data%20gaps%20and%20data%20latency%20and%20issues%20with%20Azure%26nbsp%3B%3C%2FSPAN%3E%3CFONT%20color%3D%22%23252423%22%20face%3D%22-apple-system%2C%20BlinkMacSystemFont%2C%20Segoe%20UI%2C%20system-ui%2C%20Apple%20Color%20Emoji%2C%20Segoe%20UI%20Emoji%2C%20Segoe%20UI%20Web%2C%20sans-serif%22%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3ESentinel.%3C%2FSPAN%3E%3C%2FFONT%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E%26nbsp%3BOur%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%2006%2F20%2017%3A15%20PM%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution%2C%26nbsp%3B%3C%2FSPAN%3EAdding%20Cores%20Capacity%20to%20WEU%20allowing%20the%20service%20to%20scale%20out%20did%20not%20help.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20NA%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2006%2F20%2023%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E%3CSPAN%20style%3D%22font-size%3A%2014px%3B%22%3E-Arish%20Balasubramani%3C%2FSPAN%3E%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%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%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jun 23 2022 12:38 PM
Updated by: