Turn PostgreSQL logs into incident and tuning reports with pgBadger
Use pgBadger when an agent needs to convert raw PostgreSQL logs into readable evidence about slow queries, errors, and workload hotspots after an incident.
What it does
Turn PostgreSQL logs into incident and tuning reports with pgBadger
Use pgBadger when an agent needs to convert raw PostgreSQL logs into readable evidence about slow queries, errors, and workload hotspots after an incident.
Prerequisites
pgBadger, PostgreSQL logs with compatible log settings, and a shell environment for report generation.
Installation
Use the upstream install or setup path that matches your environment:
- make && sudo make install
Requirements and caveats from upstream:
- Requires incremental output directories and the
- month. Requires incremental output directories and
- You must enable and set some configuration directives in your postgresql.conf
Basic usage or getting-started notes:
-
PostgreSQL log analyzer with fully detailed reports and graphs.
-
Arguments:
-
logfile can be a single log file, a list of files, or a shell command
-
Extracted from upstream docs: https://raw.githubusercontent.com/darold/pgbadger/HEAD/README.md
Documentation
Source
Capabilities
Install
Quality
deterministic score 0.45 from registry signals: · indexed on github topic:agent-skills · 8 github stars · SKILL.md body (1,216 chars)