Diagnose ProxySQL incidents by mapping symptoms to Netdata signal domains.
npx skills add https://github.com/netdata/skills --skill troubleshoot-proxysql
Please help me install this Agent Skill. Skill: troubleshoot-proxysql Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-proxysql Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-proxysql
It helps you rapidly diagnose and troubleshoot ProxySQL incidents such as backend connection starvation, multiplexing collapse, monitor false decisions, query rule CPU overload, and configuration drift using Netdata-observed signals.
Use the troubleshoot-proxysql skill to diagnose a live ProxySQL incident by asking an AI agent: "Diagnose why my ProxySQL is timing out and backends look unhealthy, and tell me the most likely failure archetype and what to check next in Netdata via MCP."
High-intent search queries and answers about installing and using this skill.
To troubleshoot ProxySQL backend connection starvation, you map observed failure symptoms to Netdata operator playbook signal domains. This diagnostic path uses MCP query access to verify backend health and connection pool usage metrics, providing evidence-based remediation suggestions.
Common ProxySQL failure archetypes include backend connection starvation, multiplexing collapse, monitor false decisions, query rule CPU overload, and configuration drift. Mapping these symptoms to Netdata contexts via MCP helps identify the root cause during on-call triage.
You validate ProxySQL configuration drift remediation by re-querying expected metric bands through MCP. This remediation validation loop re-checks the same load-bearing Netdata metrics after applying changes to confirm the signal drift is resolved.
Yes, you can diagnose ProxySQL multiplexing collapse using Netdata observability data. The diagnostic process queries proxysql contexts via MCP to correlate anomaly rankings and client connection metrics, identifying if multiplexing limits are causing the collapse.
Yes, MCP query access to Netdata contexts is required for ProxySQL incident response. The diagnostic skill queries proxysql metrics, correlates anomalies, and validates remediation by re-querying expected metric bands through the MCP connection.
netdataDiagnose uWSGI failure modes using Netdata signals via MCP queries.
kubuszokOrchestrates remediation campaigns by managing issue lifecycle and verifying evidence.
netdataTriage Nvidia GPU failures by mapping Netdata MCP metrics to signal-domain rule files.
rnavarychConfigure database connection pooling across PostgreSQL and MySQL engines.
