What problem does it solve?
It helps you rapidly triage and diagnose HAProxy incidents by mapping symptoms like connection saturation, backend collapse, TLS resource exhaustion, buffer starvation, reload storms, and stick-table overflow to the exact Netdata operator playbook signal domains.
Core Features & Use Cases
- Structured MCP-driven triage: Guides an AI through MCP queries (liveness, backend health, frontend/backend session and request rates, queue time) to determine which diagnostic branch to follow.
- Operator playbook signal mapping: Breaks HAProxy health into availability, throughput, latency, errors, saturation, and ssl/tls domains and routes you to the right rule file.
- Remediation verification loop: Re-runs the same MCP verification queries to confirm signals return to expected ranges after remediation.
Quick Start
Use this skill when diagnosing a production HAProxy outage by asking an AI to triage “diagnose HAProxy with connection saturation and backend 503s using Netdata MCP,” and have it run the operator-style diagnostic tree against the relevant haproxy metrics.