troubleshoot-vmware-vsphere

To troubleshoot a VMware vSphere performance incident using Netdata, this skill applies a structured diagnostic tree via MCP to query host and VM metrics, identifying failure archetypes like CPU starvation or storage latency cliffs for fast triage.

Memory pressure cascades and CPU starvation in vSphere VMs are common failure archetypes caused by resource exhaustion. This skill identifies them by correlating anomaly rankings from Netdata signals across VM-level and host-level contexts during the incident window.

To diagnose a suspected storage latency cliff on a vSphere host, ask the agent to triage the host over a specific time window using Netdata via MCP, which will pull load-bearing metrics and route through the storage domain diagnostic rules.

Yes, you can use this vSphere triage skill for on-call root cause analysis. It applies Netdata operator playbook logic to identify failure archetypes and verifies remediation by re-querying load-bearing contexts to confirm metrics return to expected ranges.

Yes, this vSphere troubleshooting skill requires an MCP connection to Netdata. It depends on MCP calls for metric discovery, metric querying over a defined time window, anomaly ranking, and remediation verification.

When troubleshooting vSphere NUMA penalties, the limitation is that diagnostic accuracy depends on the available Netdata signals. The skill routes through hardware and host health domain rules, but cannot identify archetypes if the required load-bearing metrics are missing.