Christoph Berg [Tue, 19 Feb 2019 11:45:41 +0000 (12:45 +0100)]
t/02_basics.t: Don't fail if syslog test takes more than 10s
The syslog test checks if the result is exactly 24281 bytes, but if the
run takes 10s or more, the result is longer.
Generated on Tue Feb 19 12:24:58 2019
Log file: t/fixtures/pg-syslog.1.bz2
Parsed 59,921 log entries in 19s <-- PROBLEM HERE
Log start from 2019-02-11 13:15:39 to 2019-02-11 13:16:26
Gilles Darold [Fri, 8 Feb 2019 07:42:30 +0000 (08:42 +0100)]
Fix autodetection of log file with "non standard" log line prefix. If
--prefix specify %t | %m | %n and %p or %c, set format to stderr. Thanks
to Alex Danvy for the report.
Here pgbadger will create two reports in text and html format saved
in the two corresponding file. It will also output a json report on
standard output. Thanks to Nikolay for the feature request.
Gilles Darold [Mon, 26 Nov 2018 21:43:59 +0000 (22:43 +0100)]
Add support to http or ftp remote PostgreSQL log file download.
The log file is parsed during the download using curl command
and never saved to disk. With ssh remote log parsing you can use
uri as comand line argument to specify the PostgreSQL log file.
with http and ftp protocol you need to specify the log file format
at end of the uri:
http://localhost/postgresql-10-main.log:stderr
You can specify multiple uri for log files to be parsed. This is
usefull when you have pgbouncer log file on a remote host and
PostgreSQL logs in the local host.
Old syntax to parse remote log file using -r option is still
working but is obsolete and might be removed in two or three
major versions.
Gilles Darold [Fri, 12 Oct 2018 09:19:49 +0000 (11:19 +0200)]
Add support to HTTP logfile download by pgBadger, for example:
/usr/bin/pgbadger http://www.mydom.com/postgresql-10.log
Will parse the file during download using curl command.
Christoph Berg [Mon, 10 Sep 2018 12:01:28 +0000 (14:01 +0200)]
Sync pgbadger, pod, and README, and fix some syntax errors
pgbadger, doc/pgBadger.pod, and README were out of sync. Fix by running
"make", and slight editing of pgbadger when the pod file was more
correct.
Also, the input was using "\" line-continuations which would need to be
\\ for pod to correctly handle them. Fix by formatting as a single line
instead, which is better suitable for cut-and-paste (and there's already
longer lines in the surrounding text). In plus, crontabs do not support \
anyway. In passing, fix +%F crontab example to be +\%F because % is
magic in crontabs.
Gilles Darold [Thu, 30 Aug 2018 09:11:13 +0000 (11:11 +0200)]
List of changes in this commit:
- Fix parsing of vacuum / analyze system usage for PostgreSQL 10.
Thanks to Achilleas Mantzios for the patch.
- Fix Temporary File Activity table.
- Remove dependency to git during install.
- Add support to auto_explain json output format. Thanks to dmius
for the report.
- Fix auto_explain parser and queries that was counted twice.
Thanks to zam6ak for the report.
- Add support to %q placeholder in log_line_prefix.
- Fix checkpoint regex to match PostgreSQL 10 log messages. Thanks
to Edmund Horner for the patch.
- Update description of -f | --format option by adding information
about jsonlog format.
- Fix wrong long name for option -J that should be --Jobs intead
of --job_per_file. Thanks to Chad Trabant for the report.
- Add jsonlog input format. Some users are using the jsonlog format
of Michael Paquier extension, with -f jsonlog pgbadger will be
able to parse the log.
- Fix query normalisation to not duplicate with bind queries.
Normalisation of values are now tranformed into a single ? and no
more 0 for numbers, two single quote for string. Thanks to vadv
for the report.
- Fix log level count. Thanks to Jean-Christophe Arnu for the report.
- Make pgbadger more compliant with B::Lint bare sub name.
- Made perlcritic happy.
- Add --prettify-json command line option to prettify JSON output.
Default output is all in single line.
- Fix Events distribution report.
- Fix bug with --prefix when log_line_prefix contain multiple %%.
Thanks to svb007 for the report.
- Add --log-timezone +/-XX command line option to set the number
of hours from GMT of the timezone that must be used to adjust
date/time read from log file before beeing parsed. Using this
option make more difficult log search with a date/time because the
time will not be the same in the log. Note that you might still
need to adjust the graph timezone using -Z when the client has not
the same timezone. Thanks to xdexter for the feature request.
- Apply timezone to bar chart in pgBouncer reports.
- Apply timezone to bar chart in Top queries reports.
- Apply timezone to bar chart in Most frequent errors/events report.
- Remove INDEXES from the keyword list and add BUFFERS to this list.
- Fix normalization of query using cursors.
Gilles Darold [Tue, 28 Aug 2018 20:44:26 +0000 (22:44 +0200)]
Remove Dockerfile and documentation about docker run. pgBadger comes as
a single Perl script without any dependence and it can be used on any
plateform. It is a non sens to use docker to run pgbadger, if you don't
want to install anything, just copy the file pgbadger where you want and
execute it.
Gilles Darold [Tue, 28 Aug 2018 14:51:00 +0000 (16:51 +0200)]
The badger is back to home, modify all links to new URLs
- Web site: http://pgbadger.darold.net
- Source code: https://github.com/darold/pgbadger
Change copyright year and name.
Gilles Darold [Tue, 28 Aug 2018 14:46:58 +0000 (16:46 +0200)]
The badger is back to home, modify all links to new URLs
- Web site: http://pgbadger.darold.net
- Source code: https://github.com/darold/pgbadger
Change copyright year and name.