troubleshoot-mysql

Diagnose MySQL incidents using Netdata signals queried via MCP.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you quickly diagnose why a MySQL service is failing or behaving abnormally by turning Netdata operator triage guidance into an agent-driven diagnostic workflow.

Core Features & Use Cases

  • Structured MySQL triage for common production failure archetypes: redo log stalls, connection exhaustion, purge lag explosion, metadata lock cascades, and replication lag spirals.
  • Signal-first diagnostics via MCP that queries Netdata for MySQL availability, throughput, latency, errors, saturation, resource utilization, and replication/consistency signals.
  • Rule-file guided remediation that recommends the next diagnostic step and remediation approach based on the most relevant operator playbook domain.

Use case: An on-call engineer gets paged for elevated MySQL errors and connection spikes; the agent queries the MySQL node via MCP, identifies the matching failure pattern domain, and produces a targeted remediation plan with verification queries.

Quick Start

Ask an AI coding agent: "Diagnose my MySQL incident on host <host> and recommend remediation based on Netdata operator playbook signals, using MCP queries for mysql.*."

Frequently Asked Questions about troubleshoot-mysql

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

FAQPage Schema
How do I troubleshoot MySQL replication lag and connection exhaustion incidents?

You can diagnose MySQL incidents by querying Netdata for availability, latency, and saturation signals via MCP. The Skill identifies failure archetypes like purge lag explosion or metadata lock cascades, then applies operator-playbook rule files to drive remediation.

What is the best way to triage MySQL root causes using observability signals?

The best way to triage MySQL root causes is using an agent-driven diagnostic workflow that queries Netdata MySQL signals via MCP. It matches abnormal latency, errors, or unexpected restarts against known failure archetypes to recommend targeted remediation.

Does this MySQL diagnostic workflow work with Netdata MCP queries?

Yes, this MySQL diagnostic workflow requires MCP calls for MySQL discovery and signal verification. It queries the Netdata MySQL node via MCP to check availability, throughput, latency, errors, saturation, resource utilization, and replication consistency signals.

How do I diagnose MySQL redo log stalls and metadata lock cascades?

Diagnose MySQL redo log stalls and metadata lock cascades by querying Netdata for abnormal availability and saturation signals via MCP. The Skill matches these symptoms against structured production failure archetypes to produce a targeted remediation plan with verification queries.

When should I use an agent-driven workflow for MySQL incident triage?

Use an agent-driven workflow for MySQL incident triage when the service shows abnormal availability, latency, saturation, errors, resource exhaustion, replication inconsistency, or unexpected restarts. It provides structured operator playbook guidance for targeted remediation.