pgBadger

pgBadger started out as a small Linux CLI tool that helped database administrators analyze PostgreSQL log files.

The project has seen a good adoption rate and development has evolved to produce a more complete product, now with a Web-based GUI included, written in Perl and packed with lots of cool features.

The pgBadger interface works by reading PostgreSQL log files, organizing the data, and then plotting out various data details using a JavaScript charting library.

This makes reading the log data much easier and provide a quicker and easier to understand overview of what's happening in the database.

Logs for multiple days, months, and years can be kept, and various database (logged) details can be checked out.

pgBadger currently works with normal log files, as well as gzip compressed file. The script is also able to handle log files at extremely large sizes.

What is new in this release:

• New pgbouncer reports are:
• Request Throughput
• Bytes I/O Throughput
• Queries Average duration
• Simultaneous sessions
• Histogram of sessions times
• Sessions per database
• Sessions per user
• Sessions per host
• Established connections
• Connections per database
• Connections per user
• Connections per host
• Most used reserved pools
• Most Frequent Errors/Events

What is new in version 7.3:

• Add --timezone=+/-HH to control the timezone used in charts. The javascript library runs at client side so the timezone used is the browser timezone so the displayed time in the charts can be different from the time in the log file.
• Add /tmp/pgbadger.pid file to prevent cron jobs overlaping on same log files.
• Add command line option --pid-dir to be able to run two pgbadger at the same time by setting an alternate path to the pid file.
• Report information about "LOG: skipping analyze of ..." into events reports.
• Report message "LOG: sending cancel to blocking autovacuum" into events reports. Useful to look for queries generating autovacuum kill on account of a lock issue.

What is new in version 7.1:

• New report about events distribution per 5 minutes.
• New per application details (total duration and times executed) for each query reported in Top Queries reports. The details are visible from a new button called "App(s) involved".
• Add support to auto_explain extension. EXPLAIN plan will be added together with top slowest queries when available in log file.
• New report on queries cumulated durations per user.
• New report about the Number of cancelled queries (graph)
• New report about Queries generating the most cancellation (N)
• New report about Queries most cancelled.

What is new in version 7.0:

• New report about events distribution per 5 minutes.
• New per application details (total duration and times executed) for each query reported in Top Queries reports. The details are visible from a new button called "App(s) involved".
• Add support to auto_explain extension. EXPLAIN plan will be added together with top slowest queries when available in log file.
• New report on queries cumulated durations per user.
• New report about the Number of cancelled queries (graph)
• New report about Queries generating the most cancellation (N)
• New report about Queries most cancelled.

What is new in version 6.3:

• Fixed case where die with interrupt signal is received when using -e option.
• Added a new program pgbadger_tools to demonstrate how to deal with pgBadger binary files to build your own new feature. The first one 'explain-slowest' allow printing of top slowest queries as EXPLAIN statements.
• Keep tick formatting when zooming.
• Fixed automatic detection of rsyslogd logs.
• Fixed issue in calculating min/max/avg in "General Activity" report. It was build on the sum of queries duration per minutes instead of each duration.
• The same issue remains with percentile that are build using the sum of duration per minutes and doesn't represent the real queries duration.
• This commit also include a modification in convert_time() method to reports milliseconds.
• Added -B or --bar-graph command line option to use bar instead of line in graph.
• Fixed Checkpoint Wal files usage graph title.

What is new in version 6.0:

• This new major release adds some new features like automatic cleanup of binary
• files in incremental mode or maximum number of weeks for reports retention.
• It improve the incremental mode with allowing the use of multiprocessing with
• multiple log file.
• It also adds report of query latency percentile on the general activity table
• (percentiles are 90, 95, 99).
• There's also a new output format: JSON. This format is good for sharing data
• with other languages, which makes it easy to integrate pgBadger's result into
• other monitoring tools.
• You may want to expose your reports but not the data, using the --anonymize
• option pgBadger will be able to anonymize all literal values in the queries.
• Sometime select to copy a query from the report could be a pain. There's now
• a click-to-select button in front of each query that allow you to just use
• Ctrl+C to copy it on clipboard
• The use of the new -X option also allow pgBadger to write out extra files to
• the outdir when creating incremental reports. Those files are the CSS and
• Javascript code normally repeated in each HTLM files.
• Warning: the behavior of pgBadger in incremental mode has changed. It will now
• always cleanup the output directory of all the obsolete binary file. If you were
• using those files to build your own reports, you can prevent pgBadger to remove
• them by using the --noclean option. Note that if you use the retention feature,
• all those files in obsolete directories will be removed too.