forked from pool/pgbadger
28423a5bac
Move the cron and systemd files out into the documentation directory and
include an extended README.SUSE to show how to work with them.
- update to 12.3
This is a maintenance release of pgBadger that fixes issues reported by
users since last release. It also adds some new features:
* Add option --include-pid to only report events related to a session
pid (%p). Can be used multiple time. Thanks to Henrietta Dombrovskaya
for the feature request.
* Add option --include-session to only report events related to the
session id (%c). Can be used multiple time. Thanks to Henrietta Dombrovskaya
for the feature request.
* Add option --dump-raw-csv to only parse the log and dump the information
into CSV format. No further processing is done, no report is generated.
Thanks to Henrietta Dombrovskaya for the feature request.
Here is the complete list of changes and acknowledgments:
* Update pgFormatter to version 5.5
* Fix end date of parsing with jsonlog format. Thanks to jw1u1 for the report.
* Fix typo in "Sessions per application". Thanks to fairyfar for the patch.
* Fix "INSERT/UPDATE/DELETE Traffic" chart bug. Thanks to fairyfar for the
patch.
* Fix parsing of orphan lines with bind queries. Thanks to youxq for the
report.
* Fix Analyze per table report with new PG versions. Thanks to Jean-Christophe
Arnu for the patch.
* Fix syslog entry parser when the syslog timestamp contains milliseconds.
Thanks to Pavel Rabel for the report.
- add systemd timer examples: beside the existing cron job example, this
allows people to get an idea how to automate the generation of reports
- introduce local cron macro: only recommend cron on older distributions
and leave the cron example file where it was historically (but place it
into the examples folder on newer distributions).
- get rid of old suse_version 11.3 check
OBS-URL: https://build.opensuse.org/request/show/1130189
OBS-URL: https://build.opensuse.org/package/show/server:database:postgresql/pgbadger?expand=0&rev=4
34 lines
1018 B
SYSTEMD
34 lines
1018 B
SYSTEMD
#
|
|
# The following two examples will auto-generate an report from your
|
|
# postgresql log files.
|
|
#
|
|
# You need the following settings in a standard postgresql-server
|
|
# installation in /var/lib/pgsql/data/postgresql.conf for this:
|
|
# log_filename = 'postgresql-%Y-%m-%d.log'
|
|
# log_rotation_age = 1d
|
|
# log_rotation_size = 0
|
|
#
|
|
# The output will be placed below /srv/www/htdocs/pgbadger/
|
|
#
|
|
# See https://github.com/darold/pgbadger/ for more details
|
|
#
|
|
# Note 1: Please have a look at the corresponding pgbadger.service file
|
|
# systemctl edit pgbadger.service
|
|
# and adjust it to your needs.
|
|
#
|
|
|
|
[Unit]
|
|
Description=Auto-Generate an incremental report from a postgresql logfile
|
|
|
|
[Timer]
|
|
## 1. This timer runs every day at 04:00 - and should match the first
|
|
## command in the pgbadger.service file
|
|
# OnCalendar=*-*-* 04:00:00
|
|
## 2. This timer runs every week - and should match the 2nd
|
|
## command in the pgbadger.service file
|
|
# OnCalendar=weekly
|
|
Persistent=true
|
|
|
|
[Install]
|
|
WantedBy=timers.target
|