troubleshoot-haproxy

Triage HAProxy incidents using Netdata MCP queries and operator playbooks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about troubleshoot-haproxy

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

FAQPage Schema
How do I troubleshoot HAProxy connection saturation and backend 503 errors?

To troubleshoot HAProxy connection saturation and backend 503s, run structured triage using Netdata MCP queries to analyze backend health, session rates, and queue times, then follow the mapped operator playbook diagnostic branch for remediation.

What causes TLS CPU exhaustion in HAProxy and how do I diagnose it?

TLS CPU exhaustion in HAProxy is diagnosed by querying haproxy.* metric contexts over a recent incident window with Netdata MCP, mapping the SSL/TLS resource saturation to the correct operator playbook signal domain for targeted remediation.

How can I verify an HAProxy fix after resolving buffer pool starvation?

Verify an HAProxy fix by re-running the same Netdata MCP verification queries to confirm that metrics return to expected ranges, completing a remediation verification loop for the buffer pool starvation incident.

Does Netdata work with HAProxy for diagnosing stick-table overflow and reload storms?

Yes, Netdata works with HAProxy by using MCP queries to map symptoms like stick-table overflow and reload storms to specific operator playbook signal domains, guiding structured triage for these exact availability and saturation incident scenarios.

What is the best way to monitor HAProxy backend collapse during an incident?

The best way to monitor HAProxy backend collapse during an incident is to execute liveness and backend health checks through Netdata MCP, routing the symptoms to the availability and throughput operator playbook signal domains for diagnosis.