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

Published Aug 21 2020 08:05 PM 1,577 Views
Final Update: Saturday, 22 August 2020 10:24 UTC

We've confirmed that all systems are back to normal with no customer impact as of 8/22, 10:11 UTC. Our logs show the incident started on 8/20, 18:00 UTC and that during the 2 days, 16 hours and 11minutes that it took to resolve the issue, a very small percentage of customers in all public regions may have experience data gaps with the below data types:

NETWORK_MONITORING_BLOB
ONPREM_IIS_BLOB
CUSTOM_LOG
WAD_EVENT_TABLE
ETW_EVENT_TABLE
PAASV2_TABLE
PAASV2_RELIABLE_SERVICE_TABLE
PAASV2_RELIABLE_ACTOR_TABLE
WAD_IIS_BLOB
LINUX_SYS_LOGS_TABLE
WAD_SECURITY_EVENT_TABLE
WDAV_THREAT_TABLE
WAAS_DEPLOYMENT_STATUS_TABLE
WUDO_AGGREGATED_STATUS_TABLE
WAAS_UPDATE_STATUS_TABLE
WDAV_STATUS_TABLE
WAAS_INSIDER_STATUS_TABLE
WUDO_STATUS_TABLE
MAOfficeMacroHealthIssues_TABLE
MA_OFFICEADDIN_TABLE
MAWindowsCurrencyAssessmentDailyCounts_TABLE
MA_APPLICATIONINSTANCE_TABLE
MA_PROPOSEDPILOTDEVICES_TABLE
MAOfficeCurrencyAssessmentDailyCounts_TABLE
MAWindowsBuildInfo_TABLE
MAApplicationHealthAlternativeVersions_TABLE
MA_OFFICEADDINREADINESS_TABLE
MA_APPLICATION_TABLE
MADevicePnPHealthIssues_TABLE
MAWindowsSysReqInstanceReadiness_TABLE
MAApplicationHealth_TABLE
MADeviceNotEnrolled_TABLE
MAOfficeMacroIssueReadiness_TABLE
MA_DRIVERREADINESS_TABLE
MAOfficeAddinHealthIssues_TABLE
MAWindowsCurrencyAssessment_TABLE
MAOfficeSuiteInstance_TABLE
MAOfficeMacroIssueInstanceReadiness_TABLE
MAApplicationHealthIssues_TABLE
MA_OFFICEADDININSTANCE_TABLE
MA_OFFICEAPP_TABLE
MAOfficeBuildInfo_TABLE
MAOfficeSuite_TABLE
MAOfficeAddinInstanceReadiness_TABLE
MA_DEVICE_TABLE
MADriverInstanceReadiness_TABLE
MAOfficeMacroHealth_TABLE
MA_APPLICATIONREADINESS_TABLE
MAOfficeDeploymentStatus_TABLE
MA_DEVICEREADINESS_TABLE
MA_OFFICEAPPINSTANCE_TABLE
MAOfficeAddinHealth_TABLE
MAOfficeAppInstanceHealth_TABLE
MADevicePnPHealthAlternativeVersions_TABLE
MAOfficeAppHealth_TABLE
MA_DEPLOYMENTPLAN_TABLE
MAOfficeMacroSummary_TABLE
MAApplicationInstanceReadiness_TABLE
MAOfficeCurrencyAssessment_TABLE
MADevicePnPHealth_TABLE
MAWindowsDeploymentStatus_TABLE
MA_OFFICEAPPREADINESS_TABLE
OFFICEACTIVITY_RESTAPI
MAOfficeAddinEntityHealthInfo_TABLE
MAOfficeMacroGlobalHealthInfo_TABLE
SHOEBOX_NETWORK_EVENT_LOG_BLOB
SHOEBOX_NETWORK_COUNTER_LOG_BLOB

  • Root Cause: The failure was due to a bad configuration in a recent build.
  • Incident Timeline: 2 days, 16 Hours & 11 minutes - 8/20, 18:00 UTC through 8/22, 10:11 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Eric Singleton

Update: Saturday, 22 August 2020 08:33 UTC

Engineers are in the process of finalizing the rollback of the build which was impacting the ingestion time of certain data types in all public regions. 
  • Work Around: None
  • Next Update: Before 08/22 11:00 UTC
-Eric Singleton

Update: Saturday, 22 August 2020 06:22 UTC

Engineers are still in the process of rolling back the build which was impacting the ingestion time of certain data types to a known good build. 
  • Work Around: None
  • Next Update: Before 08/22 08:30 UTC
-Eric Singleton

Update: Saturday, 22 August 2020 03:45 UTC

Root cause has been isolated to a bad configuration in a recent build which was impacting the ingestion time of certain data types causing possible data gaps and unexpectedly latent log ingestion for some customers . To address this issue we are rolling back to a known good build. 
  • Work Around: None
  • Next Update: Before 08/22 06:00 UTC
-Jeff

Initial Update: Saturday, 22 August 2020 03:03 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers in all public regions may experience data gaps for certain data types.
  • Work Around: None
  • Next Update: Before 08/22 05:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jeff

%3CLINGO-SUB%20id%3D%22lingo-sub-1605165%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2008%2F22%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1605165%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%20Saturday%2C%2022%20August%202020%2010%3A24%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%208%2F22%2C%2010%3A11%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%208%2F20%2C%2018%3A00%20UTC%20and%20that%20during%20the%202%20days%2C%2016%20hours%20and%2011minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%20a%20very%20small%20percentage%20of%20customers%20in%20all%20public%20regions%20may%20have%20experience%20data%20gaps%20with%20the%20below%20data%20types%3A%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3ENETWORK_MONITORING_BLOB%3CBR%20%2F%3E%20ONPREM_IIS_BLOB%3CBR%20%2F%3E%20CUSTOM_LOG%3CBR%20%2F%3E%20WAD_EVENT_TABLE%3CBR%20%2F%3E%20ETW_EVENT_TABLE%3CBR%20%2F%3E%20PAASV2_TABLE%3CBR%20%2F%3E%20PAASV2_RELIABLE_SERVICE_TABLE%3CBR%20%2F%3E%20PAASV2_RELIABLE_ACTOR_TABLE%3CBR%20%2F%3E%20WAD_IIS_BLOB%3CBR%20%2F%3E%20LINUX_SYS_LOGS_TABLE%3CBR%20%2F%3E%20WAD_SECURITY_EVENT_TABLE%3CBR%20%2F%3E%20WDAV_THREAT_TABLE%3CBR%20%2F%3E%20WAAS_DEPLOYMENT_STATUS_TABLE%3CBR%20%2F%3E%20WUDO_AGGREGATED_STATUS_TABLE%3CBR%20%2F%3E%20WAAS_UPDATE_STATUS_TABLE%3CBR%20%2F%3E%20WDAV_STATUS_TABLE%3CBR%20%2F%3E%20WAAS_INSIDER_STATUS_TABLE%3CBR%20%2F%3E%20WUDO_STATUS_TABLE%3CBR%20%2F%3E%20MAOfficeMacroHealthIssues_TABLE%3CBR%20%2F%3E%20MA_OFFICEADDIN_TABLE%3CBR%20%2F%3E%20MAWindowsCurrencyAssessmentDailyCounts_TABLE%3CBR%20%2F%3E%20MA_APPLICATIONINSTANCE_TABLE%3CBR%20%2F%3E%20MA_PROPOSEDPILOTDEVICES_TABLE%3CBR%20%2F%3E%20MAOfficeCurrencyAssessmentDailyCounts_TABLE%3CBR%20%2F%3E%20MAWindowsBuildInfo_TABLE%3CBR%20%2F%3E%20MAApplicationHealthAlternativeVersions_TABLE%3CBR%20%2F%3E%20MA_OFFICEADDINREADINESS_TABLE%3CBR%20%2F%3E%20MA_APPLICATION_TABLE%3CBR%20%2F%3E%20MADevicePnPHealthIssues_TABLE%3CBR%20%2F%3E%20MAWindowsSysReqInstanceReadiness_TABLE%3CBR%20%2F%3E%20MAApplicationHealth_TABLE%3CBR%20%2F%3E%20MADeviceNotEnrolled_TABLE%3CBR%20%2F%3E%20MAOfficeMacroIssueReadiness_TABLE%3CBR%20%2F%3E%20MA_DRIVERREADINESS_TABLE%3CBR%20%2F%3E%20MAOfficeAddinHealthIssues_TABLE%3CBR%20%2F%3E%20MAWindowsCurrencyAssessment_TABLE%3CBR%20%2F%3E%20MAOfficeSuiteInstance_TABLE%3CBR%20%2F%3E%20MAOfficeMacroIssueInstanceReadiness_TABLE%3CBR%20%2F%3E%20MAApplicationHealthIssues_TABLE%3CBR%20%2F%3E%20MA_OFFICEADDININSTANCE_TABLE%3CBR%20%2F%3E%20MA_OFFICEAPP_TABLE%3CBR%20%2F%3E%20MAOfficeBuildInfo_TABLE%3CBR%20%2F%3E%20MAOfficeSuite_TABLE%3CBR%20%2F%3E%20MAOfficeAddinInstanceReadiness_TABLE%3CBR%20%2F%3E%20MA_DEVICE_TABLE%3CBR%20%2F%3E%20MADriverInstanceReadiness_TABLE%3CBR%20%2F%3E%20MAOfficeMacroHealth_TABLE%3CBR%20%2F%3E%20MA_APPLICATIONREADINESS_TABLE%3CBR%20%2F%3E%20MAOfficeDeploymentStatus_TABLE%3CBR%20%2F%3E%20MA_DEVICEREADINESS_TABLE%3CBR%20%2F%3E%20MA_OFFICEAPPINSTANCE_TABLE%3CBR%20%2F%3E%20MAOfficeAddinHealth_TABLE%3CBR%20%2F%3E%20MAOfficeAppInstanceHealth_TABLE%3CBR%20%2F%3E%20MADevicePnPHealthAlternativeVersions_TABLE%3CBR%20%2F%3E%20MAOfficeAppHealth_TABLE%3CBR%20%2F%3E%20MA_DEPLOYMENTPLAN_TABLE%3CBR%20%2F%3E%20MAOfficeMacroSummary_TABLE%3CBR%20%2F%3E%20MAApplicationInstanceReadiness_TABLE%3CBR%20%2F%3E%20MAOfficeCurrencyAssessment_TABLE%3CBR%20%2F%3E%20MADevicePnPHealth_TABLE%3CBR%20%2F%3E%20MAWindowsDeploymentStatus_TABLE%3CBR%20%2F%3E%20MA_OFFICEAPPREADINESS_TABLE%3CBR%20%2F%3E%20OFFICEACTIVITY_RESTAPI%3CBR%20%2F%3E%20MAOfficeAddinEntityHealthInfo_TABLE%3CBR%20%2F%3E%20MAOfficeMacroGlobalHealthInfo_TABLE%3CBR%20%2F%3E%20SHOEBOX_NETWORK_EVENT_LOG_BLOB%3CBR%20%2F%3E%20SHOEBOX_NETWORK_COUNTER_LOG_BLOB%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20bad%20configuration%20in%20a%20recent%20build.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20days%2C%2016%20Hours%20%26amp%3B%2011%20minutes%20-%208%2F20%2C%2018%3A00%20UTC%20through%208%2F22%2C%2010%3A11%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-Eric%20Singleton%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%20Saturday%2C%2022%20August%202020%2008%3A33%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EEngineers%20are%20in%20the%20process%20of%20finalizing%20the%20rollback%20of%20the%20build%20which%20was%20impacting%20the%20ingestion%20time%20of%20certain%20data%20types%20in%20all%20public%20regions.%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%2F22%2011%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Eric%20Singleton%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%20Saturday%2C%2022%20August%202020%2006%3A22%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EEngineers%20are%20still%20in%20the%20process%20of%20rolling%20back%20the%20build%20which%20was%20impacting%20the%20ingestion%20time%20of%20certain%20data%20types%20to%20a%20known%20good%20build.%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%2F22%2008%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Eric%20Singleton%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%20Saturday%2C%2022%20August%202020%2003%3A45%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3ERoot%20cause%20has%20been%20isolated%20to%20a%20bad%20configuration%20in%20a%20recent%20build%20which%20was%20impacting%20the%20ingestion%20time%20of%20certain%20data%20types%20causing%20possible%20data%20gaps%20and%20unexpectedly%20latent%20log%20ingestion%20for%20some%20customers%20.%20To%20address%20this%20issue%20we%20are%20rolling%20back%20to%20a%20known%20good%20build.%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%2F22%2006%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Jeff%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%20Saturday%2C%2022%20August%202020%2003%3A03%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20in%20all%20public%20regions%20may%20experience%20data%20gaps%20for%20certain%20data%20types.%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%2F22%2005%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jeff%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%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1605165%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Aug 22 2020 03:28 AM
Updated by: