Experiencing Data Access Issue in Azure portal for Log Analytics - 04/28 - Resolved

Published Apr 27 2021 07:48 PM 1,247 Views
Final Update: Wednesday, 28 April 2021 02:39 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/27, 02:10 UTC. Our logs show the incident started on 04/27, 01:46 UTC and that during the 24 minutes that it took to resolve the issue 5% of customers experienced data access issues and delayed or missed alerts in South East Australia.
  • Root Cause: Engineers determined that backend storage device became unhealthy.
  • Mitigation: Engineers determined that the service is auto recovered by Azure platform.
  • Incident Timeline: 24 minutes - 04/27, 01:46 UTC through 04/27, 02:10 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Vincent

%3CLINGO-SUB%20id%3D%22lingo-sub-2300363%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Log%20Analytics%20-%2004%2F28%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300363%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%20Wednesday%2C%2028%20April%202021%2002%3A39%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2004%2F27%2C%2002%3A10%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2004%2F27%2C%2001%3A46%20UTC%20and%20that%20during%20the%2024%20minutes%26nbsp%3Bthat%20it%20took%20to%20resolve%20the%20issue%205%25%20of%20customers%20experienced%26nbsp%3B%3CSPAN%20style%3D%22color%3A%20rgb(51%2C%2051%2C%2051)%3B%20font-family%3A%20%26quot%3BSegoe%20UI%26quot%3B%3B%20font-size%3A%2014.6667px%3B%22%3Edata%20access%20issues%20and%20delayed%20or%20missed%20alerts%20in%20South%20East%20Australia.%3C%2FSPAN%3E%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20Engineers%20determined%20that%20backend%20storage%20device%20became%20unhealthy.%3CBR%20%2F%3E%3C%2FLI%3E%3CLI%3E%3CU%3EMitigation%3C%2FU%3E%3A%20Engineers%20determined%20that%20the%20service%20is%20auto%20recovered%20by%20Azure%20platform.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2024%20minutes%20-%2004%2F27%2C%2001%3A46%20UTC%20through%2004%2F27%2C%2002%3A10%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-Vincent%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Apr 27 2021 07:48 PM
Updated by: