Failures in Azure Monitor in West Europe - 12/01 - Resolved

Published Dec 01 2020 08:54 AM 1,109 Views
Final Update: Tuesday, 01 December 2020 16:35 UTC

We've confirmed that all systems are back to normal with no customer impact as of 12/1, 16:30 UTC. Our logs show the incident started on 12/1, 13:35 UTC and that during the 2 Hours & 55 minutes that it took to resolve the issue customers using Application Insights and/or Azure Log Analytics in West Europe may have experienced latency/failures when accessing application data and misfired/failed alerts for these resources.

Root Cause: The failure was due to a backend service that became unhealthy due to high CPU usage causing impact to these services.
Incident Timeline: 2 Hours & 55 minutes - 12/1, 13:35 UTC through 12/1, 16:30 UTC

We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Ian

%3CLINGO-SUB%20id%3D%22lingo-sub-1945148%22%20slang%3D%22en-US%22%3EFailures%20in%20Azure%20Monitor%20in%20West%20Europe%20-%2012%2F01%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1945148%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22%22%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22text-decoration-line%3A%20underline%3B%22%3EFinal%20Update%3A%3C%2FSPAN%3E%20Tuesday%2C%2001%20December%202020%2016%3A35%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22text-decoration-line%3A%20underline%3B%22%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2012%2F1%2C%2016%3A30%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2012%2F1%2C%2013%3A35%20UTC%20and%20that%20during%20the%202%20Hours%20%26amp%3B%2055%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20using%20Application%20Insights%20and%2For%20Azure%20Log%20Analytics%20in%20West%20Europe%20may%20have%20experienced%20latency%2Ffailures%20when%20accessing%20application%20data%20and%20misfired%2Ffailed%20alerts%20for%20these%20resources.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22text-decoration-line%3A%20underline%3B%22%3ERoot%20Cause%3C%2FSPAN%3E%3A%20The%20failure%20was%20due%20to%20a%20backend%20service%20that%20became%20unhealthy%20due%20to%20high%20CPU%20usage%20causing%20impact%20to%20these%20services.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22text-decoration-line%3A%20underline%3B%22%3EIncident%20Timeline%3C%2FSPAN%3E%3A%202%20Hours%20%26amp%3B%2055%20minutes%20-%2012%2F1%2C%2013%3A35%20UTC%20through%2012%2F1%2C%2016%3A30%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3E-Ian%3C%2FDIV%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1945148%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:
‎Dec 01 2020 08:54 AM
Updated by: