troubleshoot-postgresql

Diagnose PostgreSQL incidents using Netdata MCP queries and structured triage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you rapidly triage PostgreSQL incidents by identifying likely failure archetypes (connection exhaustion, lock contention cascades, autovacuum starvation/bloat, transaction ID wraparound emergencies, checkpoint storms, and replication lag spirals) and validating them with the same Netdata signals used by the operator playbook.

Core Features & Use Cases

  • Structured diagnostic tree for PostgreSQL: Guides an AI operator through a deterministic triage order aligned to Netdata’s PostgreSQL playbook domains (Availability, Throughput, Latency, Internal State, Replication, Security & Integrity).
  • Signal-driven MCP verification: Uses Netdata MCP query patterns to confirm process liveness, recovery state, connection health, transaction/row throughput, and domain-specific metrics before recommending remediation.
  • Archetype-focused remediation guidance: Connects observed anomalies to likely root causes and suggests next remediation steps with “re-run to verify” validation behavior.

Quick Start

Ask an AI agent: "Diagnose my PostgreSQL incident using Netdata via MCP and recommend the most likely remediation after verification."

Frequently Asked Questions about troubleshoot-postgresql

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

FAQPage Schema
How do I troubleshoot PostgreSQL connection exhaustion and lock contention during an incident?

To troubleshoot PostgreSQL connection exhaustion and lock contention, this skill applies a structured diagnostic tree using Netdata MCP queries to verify process liveness, connection health, and transaction rates, confirming the failure archetype before recommending remediation.

What causes transaction ID wraparound emergencies in PostgreSQL and how do I detect them?

Transaction ID wraparound emergencies in PostgreSQL are detected by querying Netdata observability contexts for internal state anomalies and recovery status, allowing the diagnostic tree to identify this specific failure archetype during on-call triage.

Does this PostgreSQL triage process work with Netdata MCP for query analysis?

Yes, the PostgreSQL triage process works with Netdata MCP by querying specified observability contexts to analyze query duration distribution, replication health, and row operation rates to validate incident root causes.

How do I diagnose checkpoint storms and autovacuum starvation in PostgreSQL?

Diagnose checkpoint storms and autovacuum starvation in PostgreSQL by applying the skill's deterministic diagnostic tree to query Netdata metrics, checking anomalous throughput and internal state metrics over defined time windows to confirm the archetype.

What is the best way to verify PostgreSQL remediation after an on-call incident triage?

The best way to verify PostgreSQL remediation is by re-querying the same Netdata verification contexts via MCP used during diagnosis, validating that anomalous metrics across availability, throughput, and replication domains have returned to normal.