Experiencing Data Access Issue in Azure portal for Azure Monitor - 02/26 - Resolved

Published 02-25-2021 09:00 PM 1,275 Views
Final Update: Friday, 26 February 2021 08:34 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/26, 08:11 UTC. Our logs show the incident started on 02/26, 03:25 UTC and that during the 4 hours 45 Minutes that it took to resolve the issue some customers may have experienced data access, data latency and incorrect alert activations in Japan East region.
  • Root Cause: The failure was due to issue in one of our dependent service.
  • Incident Timeline: 4 Hours & 45 minutes - 02/26, 03:25 UTC through 02/26, 08:11 UTC
We understand that customers rely on Azure Monitor Service as a critical service and apologize for any impact this incident caused.

-Vamshi

Initial Update: Friday, 26 February 2021 04:57 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delayed or missed Log Search Alerts in Japan East region.
  • Work Around: None
  • Next Update: Before 02/26 09:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Vamshi

%3CLINGO-SUB%20id%3D%22lingo-sub-2167838%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20in%20Azure%20portal%20for%20Azure%20Monitor%20-%2002%2F26%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2167838%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3E%3CU%20style%3D%22%22%3EFinal%20Update%3C%2FU%3E%3A%20Friday%2C%2026%20February%202021%2008%3A34%20UTC%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20We've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F26%2C%2008%3A11%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F26%2C%2003%3A25%20UTC%20and%20that%20during%20the%204%20hours%2045%20Minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20data%20access%2C%20data%20latency%20and%20incorrect%20alert%20activations%20in%20Japan%20East%20region.%3C%2FSPAN%3E%3CUL%20style%3D%22%22%3E%0A%0A%20%0A%3CLI%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issue%20in%20one%20of%20our%20dependent%20service.%20%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%204%20Hours%20%26amp%3B%2045%20minutes%20-%2002%2F26%2C%2003%3A25%20UTC%20through%2002%2F26%2C%2008%3A11%20UTC%20%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20Service%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20-Vamshi%3C%2FSPAN%3E%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Friday%2C%2026%20February%202021%2004%3A57%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20delayed%20or%20missed%20Log%20Search%20Alerts%20in%20Japan%20East%20region.%3CBR%20%2F%3E%3C%2FSPAN%3E%3CUL%3E%3CLI%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2002%2F26%2009%3A00%20UTC%20%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Vamshi%3C%2FSPAN%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%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2167838%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Feb 26 2021 12:48 AM
Updated by: