troubleshoot-nvme

Troubleshoot NVMe health by querying Netdata via MCP and mapping anomalies to playbook domains.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/netdata/skills --skill troubleshoot-nvme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-nvme
Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-nvme
Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-nvme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you rapidly triage and remediate NVMe issues (availability problems, health/critical warnings, errors, and wear degradation) by turning Netdata operator playbook logic into an MCP-driven investigation workflow.

Core Features & Use Cases

  • Structured triage across NVMe signal domains: guides an agent through Availability, Health & Critical Warnings, Errors, Endurance & Wear, Thermal, Power & Shutdown, and more via rule files.
  • Read-only MCP verification loop: queries Netdata for the relevant nvme.* chart contexts and checks whether signals return to expected ranges after proposed remediation.
  • Root-cause correlation and anomaly framing: uses anomaly ranking and correlation (including host-level context) to avoid stopping at the first misleading symptom.
  • Use case: an on-call engineer sees an alert tied to a specific NVMe instance and needs a repeatable path to determine whether the failure is controller state, critical warning bits, media integrity errors, unsafe shutdowns, or endurance/wear-related risk.

Quick Start

Ask an AI coding agent to troubleshoot the failing NVMe by querying Netdata via MCP and applying the NVMe diagnostic tree to recommend the next remediation step.

Frequently Asked Questions about troubleshoot-nvme

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot NVMe critical warnings and media errors using Netdata?

Troubleshoot NVMe critical warnings by querying Netdata via MCP to map observed anomalies to operator playbook domains, checking health bits, media integrity errors, and recommending targeted remediation.

What is the best way to diagnose NVMe drive health during incident response?

Diagnose NVMe drive health by running read-only MCP calls like find_anomalous_metrics and find_correlated_metrics to identify root causes across availability, endurance, thermal, and power domains.

Can I verify NVMe signal recovery after applying remediation steps?

Verify NVMe signal recovery by re-running the same MCP verification window after remediation to query load-bearing nvme.* chart contexts and confirm signals return to expected ranges.

Does Netdata MCP support correlating NVMe anomalies with host-level metrics?

Netdata MCP supports correlating NVMe anomalies with host-level context using anomaly ranking and correlation to prevent stopping at the first misleading symptom during triage.

Why does my NVMe controller show unsafe shutdowns and thermal transitions?

NVMe unsafe shutdowns and thermal transitions are diagnosed by querying Netdata via MCP to map anomalies to the power and thermal management domains of the NVMe operator playbook.

What Netdata MCP calls are needed to triage elevated NVMe endurance and wear degradation?

Triage NVMe endurance and wear degradation by executing list_nodes, query_metrics, list_raised_alerts, and find_anomalous_metrics to verify load-bearing nvme.* contexts and recommend remediation.