troubleshoot-pgbouncer

Diagnose PgBouncer failures via Netdata telemetry and MCP metric queries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps you quickly diagnose why PgBouncer is failing or degrading—specifically pool exhaustion, connection limits, file descriptor exhaustion, backend unreachable states, and pool mode mismatches.

Core Features & Use Cases

  • Operator playbook triage flow via MCP: walks an agent through a structured diagnostic tree using the same Netdata signal surface as the PgBouncer operator playbook.
  • Root-cause archetype matching: identifies the dominant failure mode and narrows investigation to the load-bearing signals and related contexts.
  • Verification-driven remediation: recommends remediation pointers and validates improvements by re-running the MCP queries and checking for signal recovery.

Use case: An on-call engineer is alerted because a PgBouncer instance shows rising errors/latency; this skill guides the agent through MCP queries, finds anomalous pgbouncer.* contexts, and produces a remediation path focused on the most likely archetype.

Quick Start

Ask the agent to troubleshoot PgBouncer using Netdata MCP by running the PgBouncer health queries over the last 15 to 30 minutes and selecting the correct remediation based on the detected failure archetype.

Frequently Asked Questions about troubleshoot-pgbouncer

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

FAQPage Schema
How do I troubleshoot PgBouncer connection pool exhaustion?

Troubleshoot PgBouncer pool exhaustion by querying Netdata telemetry via MCP to analyze pgbouncer.* contexts, identify anomalous metrics, and match the failure archetype to apply the correct remediation.

Why does PgBouncer show high latency and rising errors?

PgBouncer latency and errors often indicate backend unreachable states, file descriptor exhaustion, or pool mode mismatches; diagnose these by running health queries over the last 15 to 30 minutes using Netdata MCP.

What is the best way to triage PgBouncer incidents with Netdata?

Triage PgBouncer incidents by running a structured diagnostic flow via MCP that ranks anomalous pgbouncer.* metrics, narrows root-cause investigation, and verifies signal recovery after remediation.

Can I detect PgBouncer file descriptor exhaustion using Netdata metrics?

Yes, Netdata MCP queries pgbouncer.* contexts to detect file descriptor exhaustion by identifying anomalous connection behavior signals and verifying load-bearing charts during incident triage.

How do I verify PgBouncer remediation after fixing a connection issue?

Verify PgBouncer remediation by re-running MCP queries against Netdata charts to check for signal recovery and confirm the anomaly ranking no longer flags the previously detected failure archetype.

Does PgBouncer troubleshooting with Netdata require specific pool mode configurations?

PgBouncer troubleshooting with Netdata identifies pool mode mismatches as a failure archetype, so the skill applies regardless of configuration but uses telemetry signals to detect mode-related anomalies.