Advancing Azure Virtual Machine availability transparency

%3CLINGO-SUB%20id%3D%22lingo-sub-2632081%22%20slang%3D%22en-US%22%3EAdvancing%20Azure%20Virtual%20Machine%20availability%20transparency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2632081%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%20class%3D%22x-hidden-focus%22%3EWritten%20by%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20title%3D%22Mark%20Russinovich's%20blog%20archive%22%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Fauthor%2Fmarkruss%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMark%20Russinovich%3C%2FA%3E%2C%20Chief%20Technology%20Officer%20and%20Technical%20Fellow%2C%20Microsoft%20Azure%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CBLOCKQUOTE%3E%0A%3CP%3E%E2%80%9CThroughout%20our%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20title%3D%22Advancing%20Reliability%20blog%20series%20listing%22%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Ftag%2Fadvancing-reliability%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAdvancing%20Reliability%20blog%20series%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Ewe%E2%80%99ve%20explained%20various%20techniques%20used%20by%20the%20Azure%20platform%20to%20prevent%20technical%20issues%20from%20impacting%20customers%E2%80%99%20virtual%20machines%20(VMs)%20or%20other%20resources%E2%80%94like%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20title%3D%22Improving%20Azure%20Virtual%20Machines%20resiliency%20with%20Project%20Tardigrade%22%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Fimproving-azure-virtual-machines-resiliency-with-project-tardigrade%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehost%20resiliency%20with%20Project%20Tardigrade%3C%2FA%3E%2C%20cautious%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20title%3D%22Advancing%20safe%20deployment%20practices%22%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Fadvancing-safe-deployment-practices%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Esafe%20deployment%20practices%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Etaking%20advantage%20of%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20title%3D%22Advancing%20safe%20deployment%20with%20AIOps%E2%80%94introducing%20Gandalf%22%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Fadvancing-safe-deployment-with-aiops-introducing-gandalf%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EML-based%20AIOps%20insights%3C%2FA%3E%2C%20as%20well%20as%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20title%3D%22Advancing%20failure%20prediction%20and%20mitigation%E2%80%94introducing%20Narya%22%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Fadvancing-failure-prediction-and-mitigation-introducing-narya%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Epredicting%20and%20mitigating%20hardware%20failures%20with%20Project%20Narya%3C%2FA%3E.%20Despite%20these%20efforts%2C%20when%20operating%20at%20the%20scale%20of%20Azure%20we%20know%20that%20there%20will%20inevitably%20be%20some%20failures%20that%20impact%20customer%20resources%E2%80%94so%20when%20they%20do%2C%20we%20strive%20for%20transparency%20in%20how%20we%20communicate%20to%20impacted%20customers.%20So%20for%20today%E2%80%99s%20post%20in%20the%20series%2C%20I%20have%20asked%20Principal%20Software%20Engineering%20Manager%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3ENick%20Swanson%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eto%20highlight%20recent%20improvements%20in%20the%20space%E2%80%94specifically%2C%20how%20we%20surface%20more%20detailed%20root%20cause%20statements%20via%20Azure%20resource%20health.%E2%80%9D%E2%80%94%20Mark%20Russinovich%2C%20CTO%2C%20Azure%3C%2FP%3E%0A%3C%2FBLOCKQUOTE%3E%0A%3CP%3EThe%20existing%20Azure%20resource%20health%20feature%20helps%20you%20to%20diagnose%20and%20get%20support%20for%20service%20problems%20that%20affect%20your%20Azure%20resources.%20It%20reports%20on%20the%20current%20and%20past%20health%20of%20your%20resources%2C%20showing%20any%20time%20ranges%20that%20each%20of%20your%20resources%20have%20been%20unavailable.%20But%20we%20know%20that%20our%20customers%20and%20partners%20are%20particularly%20interested%20in%20%E2%80%9Cthe%20why%E2%80%9D%20to%20understand%20what%20caused%20the%20underlying%20technical%20issue%2C%20and%20in%20improving%20how%20they%20can%20receive%20communications%20about%20any%20issues%E2%80%94to%20feed%20into%20monitoring%20processes%2C%20to%20explain%20hiccups%20to%20other%20stakeholders%2C%20and%20ultimately%20to%20inform%20business%20decisions.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--382986554%22%20id%3D%22toc-hId--382986522%22%3E%3CSPAN%20class%3D%22mpp-c-heading-3%22%3EIntroducing%20root%20causes%20for%20VM%20issues%E2%80%94in%20Azure%20resource%20health%3C%2FSPAN%3E%3C%2FH2%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3CBR%20%2F%3EWe%20recently%20shipped%20an%20improvement%20to%20the%20resource%20health%20experience%20that%20will%20enhance%20the%20information%20we%20share%20with%20customers%20about%20VM%20failures%2C%20with%20additional%20context%20on%20the%20root%20cause%20that%20led%20to%20the%20issue.%20Now%2C%20in%20addition%20to%20getting%20a%20fast%20notification%20when%20a%20VM%E2%80%99s%20availability%20is%20impacted%2C%20customers%20can%20expect%20a%20root%20cause%20to%20be%20added%20at%20a%20later%20point%20once%20our%20automated%20Root%20Cause%20Analysis%20(RCA)%20system%20identifies%20the%20failing%20Azure%20platform%20component%20that%20led%20to%20the%20VM%20failure.%20Let%E2%80%99s%20walk%20through%20an%20example%20to%20see%20how%20this%20works%20in%20practice%3A%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22x-hidden-focus%22%3E%3CA%20title%3D%22Advancing%20Azure%20Virtual%20Machine%20availability%20transparency%22%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fblog%2Fadvancing-azure-virtual-machine-availability-transparency%2F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3E%3CSTRONG%3ERead%20the%20full%20article%3C%2FSTRONG%3E%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Written by Mark Russinovich, Chief Technology Officer and Technical Fellow, Microsoft Azure

 

“Throughout our Advancing Reliability blog series we’ve explained various techniques used by the Azure platform to prevent technical issues from impacting customers’ virtual machines (VMs) or other resources—like host resiliency with Project Tardigrade, cautious safe deployment practices taking advantage of ML-based AIOps insights, as well as predicting and mitigating hardware failures with Project Narya. Despite these efforts, when operating at the scale of Azure we know that there will inevitably be some failures that impact customer resources—so when they do, we strive for transparency in how we communicate to impacted customers. So for today’s post in the series, I have asked Principal Software Engineering Manager Nick Swanson to highlight recent improvements in the space—specifically, how we surface more detailed root cause statements via Azure resource health.”— Mark Russinovich, CTO, Azure

The existing Azure resource health feature helps you to diagnose and get support for service problems that affect your Azure resources. It reports on the current and past health of your resources, showing any time ranges that each of your resources have been unavailable. But we know that our customers and partners are particularly interested in “the why” to understand what caused the underlying technical issue, and in improving how they can receive communications about any issues—to feed into monitoring processes, to explain hiccups to other stakeholders, and ultimately to inform business decisions.

 

Introducing root causes for VM issues—in Azure resource health

 
We recently shipped an improvement to the resource health experience that will enhance the information we share with customers about VM failures, with additional context on the root cause that led to the issue. Now, in addition to getting a fast notification when a VM’s availability is impacted, customers can expect a root cause to be added at a later point once our automated Root Cause Analysis (RCA) system identifies the failing Azure platform component that led to the VM failure. Let’s walk through an example to see how this works in practice:

 

Read the full article

0 Replies