Experiencing Data Access Issue in Azure portal for Log Analytics - 08/01 - Resolved

Published Aug 01 2021 11:29 AM 1,519 Views
Final Update: Tuesday, 03 August 2021 07:01 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/03, 03:00 UTC. Our logs show the incident started on 08/01, 15:30 UTC and that during the  1 Day 11 Hours & 30 minutes that it took to resolve the issue. Some customers may have experienced delay in data ingestion, duplicated data and delayed or missed alerts in West US2 region
  • Root Cause: The failure was due to an issue with one of the dependent services.
  • Incident Timeline: 1 Day 11 Hours & 30 minutes - 08/01, 15:30 UTC through 08/03, 03:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Vyom

Update: Tuesday, 03 August 2021 05:08 UTC

Root cause has been isolated to configuration change which was impacting the data ingestion in the Log Analytics Workspace in West US 2 region. Some customers may continue to experience missing alerts and data and we estimate it may take few more hours before all missing alerts and data to be made available.
  • Work Around: None
  • Next Update: Before 08/03 11:30 UTC
-Vyom

Update: Monday, 02 August 2021 22:23 UTC

***** REPOSTING COMMS AS NO UPDATE FROM ENGINEERING TEAM ****
Root cause has been isolated to configuration change which was impacting the data ingestion in the Log Analytics Workspace in West US 2 region. Some customers may continue to experience missing alerts and data and we estimate it may take more hours before all missing alerts and data to be made available.
  • Work Around: None
  • Next Update: Before 08/03 04:30 UTC
-Arish B

Update: Monday, 02 August 2021 17:26 UTC
***** REPOSTING COMMS AS NO UPDATE FROM ENGINEERING TEAM ****
Root cause has been isolated to configuration change which was impacting the data ingestion in the Log Analytics Workspace in West US 2 region. Some customers may continue to experience missing alerts and data and we estimate it may take more hours before all missing alerts and data to be made available.
  • Work Around: None
  • Next Update: Before 08/02 22:00 UTC
-v-arishb

Update: Monday, 02 August 2021 10:57 UTC

Root cause has been isolated to configuration change which was impacting the data ingestion in the Log Analytics Workspace in West US 2 region. Some customers may continue to experience missing alerts and data and we estimate it may take more hours before all missing alerts and data to be made available.
  • Work Around: None
  • Next Update: Before 08/02 17:00 UTC
-Rahul

Update: Monday, 02 August 2021 07:35 UTC

Root cause has been isolated to configuration change which was impacting the data ingestion in the Log Analytics Workspace in West US 2 region. Some customers may experience missing alerts and data and we estimate it may take few more hours before all missing alerts and data to be made available.
  • Work Around: None
  • Next Update: Before 08/02 12:00 UTC
-Rahul

Update: Monday, 02 August 2021 04:12 UTC
***** REPOSTING COMMS AS NO UPDATE FROM ENGINEERING TEAM ****
Root cause has been isolated to miss configuration of some of WUS2 log analytics backend clusters which was impacting the data ingestion leading to missing alerts and data. To address this issue we applied missing configuration to some of WUS2 Log analytics Backend servers. The service is processing the backlog ingestion data which should take ~2 hours. Some customers may experience missing alerts and data and we estimate several hours before all missing alerts and data to be made available.
  • Work Around: none
  • Next Update: Before 08/02 03:30 UTC
-v-arishb

Update: Sunday, 01 August 2021 23:14 UTC

Root cause has been isolated to miss configuration of some of WUS2 log analytics backend clusters which was impacting the data ingestion leading to missing alerts and data. To address this issue we applied missing configuration to some of WUS2 Log analytics Backend servers. The service is processing the backlog ingestion data which should take ~2 hours. Some customers may experience missing alerts and data and we estimate several hours before all missing alerts and data to be made available.
  • Work Around: none
  • Next Update: Before 08/02 03:30 UTC
-v-arishb

Initial Update: Sunday, 01 August 2021 18:27 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delay in data ingestion into Log Analytics in West US2 .
  • Work Around:
  • Next Update: Before 08/01 22:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Subhash

%3CLINGO-SUB%20id%3D%22lingo-sub-2597338%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2008%2F01%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2597338%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%2003%20August%202021%2007%3A01%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2008%2F03%2C%2003%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F01%2C%2015%3A30%20UTC%26nbsp%3Band%20that%20during%20the%26nbsp%3B%26nbsp%3B1%20Day%2011%20Hours%20%26amp%3B%2030%20minutes%26nbsp%3Bthat%20it%20took%20to%20resolve%20the%20issue.%20Some%20customers%20may%20have%20experienced%20delay%20in%20data%20ingestion%2C%20duplicated%20data%20and%20delayed%20or%20missed%20alerts%20in%20West%20US2%20region%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20with%20one%20of%20the%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Day%2011%20Hours%20%26amp%3B%2030%20minutes%20-%2008%2F01%2C%2015%3A30%20UTC%20through%2008%2F03%2C%2003%3A00%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-Vyom%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%2003%20August%202021%2005%3A08%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20configuration%20change%20which%20was%20impacting%20the%20data%20ingestion%20in%20the%20Log%20Analytics%20Workspace%20in%20West%20US%202%20region.%20Some%20customers%20may%20continue%20to%20experience%20missing%20alerts%20and%20data%20and%20we%20estimate%20it%20may%20take%20few%20more%20hours%20before%20all%20missing%20alerts%20and%20data%20to%20be%20made%20available.%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%2F03%2011%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Vyom%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%2002%20August%202021%2022%3A23%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E*****%20REPOSTING%20COMMS%20AS%20NO%20UPDATE%20FROM%20ENGINEERING%20TEAM%20****%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20configuration%20change%20which%20was%20impacting%20the%20data%20ingestion%20in%20the%20Log%20Analytics%20Workspace%20in%20West%20US%202%20region.%20Some%20customers%20may%20continue%20to%20experience%20missing%20alerts%20and%20data%20and%20we%20estimate%20it%20may%20take%20more%20hours%20before%20all%20missing%20alerts%20and%20data%20to%20be%20made%20available.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%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%2008%2F03%2004%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Arish%20B%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%2002%20August%202021%2017%3A26%20UTC%3CBR%20%2F%3E*****%20REPOSTING%20COMMS%20AS%20NO%20UPDATE%20FROM%20ENGINEERING%20TEAM%20****%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20configuration%20change%20which%20was%20impacting%20the%20data%20ingestion%20in%20the%20Log%20Analytics%20Workspace%20in%20West%20US%202%20region.%20Some%20customers%20may%20continue%20to%20experience%20missing%20alerts%20and%20data%20and%20we%20estimate%20it%20may%20take%20more%20hours%20before%20all%20missing%20alerts%20and%20data%20to%20be%20made%20available.%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%2F02%2022%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-v-arishb%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%2002%20August%202021%2010%3A57%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20configuration%20change%20which%20was%20impacting%20the%20data%20ingestion%20in%20the%20Log%20Analytics%20Workspace%20in%20West%20US%202%20region.%20Some%20customers%20may%20continue%20to%20experience%20missing%20alerts%20and%20data%20and%20we%20estimate%20it%20may%20take%20more%20hours%20before%20all%20missing%20alerts%20and%20data%20to%20be%20made%20available.%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%2F02%2017%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Rahul%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%2002%20August%202021%2007%3A35%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20configuration%20change%20which%20was%20impacting%20the%20data%20ingestion%20in%20the%20Log%20Analytics%20Workspace%20in%20West%20US%202%20region.%20Some%20customers%20may%20experience%20missing%20alerts%20and%20data%20and%20we%20estimate%20it%20may%20take%20few%20more%20hours%20before%20all%20missing%20alerts%20and%20data%20to%20be%20made%20available.%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%2F02%2012%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Rahul%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%2002%20August%202021%2004%3A12%20UTC%3CBR%20%2F%3E*****%20REPOSTING%20COMMS%20AS%20NO%20UPDATE%20FROM%20ENGINEERING%20TEAM%20****%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%26nbsp%3B%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3Emiss%20configuration%20of%20some%20of%20WUS2%20log%20analytics%20backend%20clusters%3C%2FSPAN%3E%26nbsp%3Bwhich%20was%20impacting%20the%20data%20ingestion%20leading%20to%20missing%20alerts%20and%20data.%20To%20address%20this%20issue%20we%20applied%20missing%20configuration%20to%20some%20of%20WUS2%20Log%20analytics%20Backend%20servers.%26nbsp%3B%3CSPAN%20segoe%3D%22%22%20ui%3D%22%22%3EThe%20service%20is%20processing%20the%20backlog%20ingestion%20data%20which%20should%20take%20~2%20hours.%3C%2FSPAN%3E%26nbsp%3BSome%20customers%20may%20experience%20missing%20alerts%20and%20data%20and%20we%20estimate%20several%20hours%20before%20all%20missing%20alerts%20and%20data%20to%20be%20made%20available.%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%2F02%2003%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-v-arishb%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%20Sunday%2C%2001%20August%202021%2023%3A14%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%26nbsp%3B%3CSPAN%20style%3D%22color%3A%20rgb(36%2C%2036%2C%2036)%3B%20font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3Emiss%20configuration%20of%20some%20of%20WUS2%20log%20analytics%20backend%20clusters%3C%2FSPAN%3E%26nbsp%3Bwhich%20was%20impacting%20the%20data%20ingestion%20leading%20to%20missing%20alerts%20and%20data.%20To%20address%20this%20issue%20we%20applied%20missing%20configuration%20to%20some%20of%20WUS2%20Log%20analytics%20Backend%20servers.%26nbsp%3B%3CSPAN%20style%3D%22color%3A%20rgb(36%2C%2036%2C%2036)%3B%20font-family%3A%20%22%20segoe%3D%22%22%20ui%3D%22%22%3EThe%20service%20is%20processing%20the%20backlog%20ingestion%20data%20which%20should%20take%20~2%20hours.%3C%2FSPAN%3E%26nbsp%3BSome%20customers%20may%20experience%20missing%20alerts%20and%20data%20and%20we%20estimate%20several%20hours%20before%20all%20missing%20alerts%20and%20data%20to%20be%20made%20available.%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%2F02%2003%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-v-arishb%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%20Sunday%2C%2001%20August%202021%2018%3A27%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20delay%20in%20data%20ingestion%20into%20Log%20Analytics%20in%20West%20US2%20.%3CBR%20%2F%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%2008%2F01%2022%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Subhash%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%2FLINGO-BODY%3E
Version history
Last update:
‎Aug 03 2021 12:08 AM
Updated by: