postgresql-log-analyzer

Analyzes Patroni and PostgreSQL logs to identify and correlate error patterns across Kubernetes clusters.

1|3|Updated Mar 23, 2026

Search Tags:#timeline #postgresql #logs #kubernetes #diagnostics #incident-response #patroni

Ready to run

npx skills add https://github.com/IldarMinaev/troubleshooting-skill --skill postgresql-log-analyzer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postgresql-log-analyzer
Source: https://github.com/IldarMinaev/troubleshooting-skill/tree/main/skills/postgresql-log-analyzer
Command: npx skills add https://github.com/IldarMinaev/troubleshooting-skill --skill postgresql-log-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzing Patroni and PostgreSQL container logs to surface error patterns and correlate events for faster diagnosis and remediation.

Core Features & Use Cases

Surface FATAL, OOM, disk-full, connection issues, and deadlocks from Patroni and PostgreSQL logs.
Correlate log events with timeline and Patroni reconfiguration events to diagnose failovers and restarts.
Use Case: When a pod restarts or a failover occurs, quickly determine root cause by cross-referencing logs, Kubernetes events, and operator messages.

Quick Start

Analyze recent Patroni and PostgreSQL logs to surface critical errors and timeline correlations.

Frequently Asked Questions about postgresql-log-analyzer

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

FAQPage Schema

How do I analyze PostgreSQL logs to find the root cause of a pod restart or failover?▼

You can analyze PostgreSQL logs for pod restarts or failovers by parsing Patroni and PostgreSQL container logs to surface FATAL errors, OOM, and disk-full events, then correlating them with Kubernetes operator events and timeline context.

What is the best way to detect deadlocks and connection issues in a Kubernetes PostgreSQL cluster?▼

Detecting deadlocks and connection issues in a Kubernetes PostgreSQL cluster involves parsing Patroni and PostgreSQL container logs to identify specific error patterns and surface them alongside timeline context and Patroni reconfiguration events.

Can I use this log analyzer for post-incident analysis on Patroni deployments?▼

Yes, you can use this log analyzer for post-incident analysis on Patroni deployments. It applies to Kubernetes environments using the pgskipper-operator to cross-reference logs, Kubernetes events, and operator messages after an incident.

Does the analyzer work with Kubernetes deployments using the pgskipper-operator?▼

Yes, the analyzer works with Kubernetes deployments using the pgskipper-operator. It is specifically designed to apply to these environments for real-time diagnostics and post-incident log analysis.

Why does my PostgreSQL cluster failover, and how do I correlate the logs?▼

Your PostgreSQL cluster may failover due to FATAL errors, OOM, disk-full conditions, or connection issues. You can correlate the logs by cross-referencing Patroni reconfiguration events and Kubernetes operator messages with container log timelines.