check_pgactivity v2.5 has been released on November 24th 2020 under PostgreSQL
license.

check_pgactivity is a PostgreSQL plugin for Nagios and derivatives. This plugin 
is written
with a focus on a rich perfdata set. Every new features of PostgreSQL can be
easily monitored with check_pgactivity.

Changelog :

* add: new `oldest_xmin` service
* add: new `extensions_versions` service
* add: new `checksum_errors` service
* add: support for v13 and other improvements on `replication_slots`
* add: v13 compatibility for service `wal_files`
* add: various documentation details and examples
* add: support service `replication_slots` on standby
* add: accept single `b` or `o` as size unit
* add: json and json_strict output formats
* add: `size` and/or `delta` thresholds for `database_size` service
* add: thresholds are now optional for service `database_size`
* add: support for v12 and v13 `archive_folder`
* regression: threshold `repslot` becomes `spilled` in service
  `replication_slots`
* regression: in services latest_vacuum and latest_analyze: a critical alert is
  now raised on tables that were never analyzed/vacuumed or whose maintenance
  date was lost due to a crash
* fix: avoid alerts for lack of maintenance on inactive db
* fix: forbid rare cases of division by zero in `wal_files`
* fix: do not alert on missing file in `temp_files` for v10+
* fix: detect lack of maintenance in `last_vacuum` and `last_analyze` for never
  maintained tables
* fix: backend count for v10+
* fix: replace NaN with "U" for strict outputs
* fix: do not count walsenders as part of `max_connections`
* fix: broken `archiver` service with v10+
* fix: perl warning when archiver is not active

Here are some useful links:

* github repo: <https://github.com/OPMDG/check_pgactivity>
* reporting issues: <https://github.com/OPMDG/check_pgactivity/issues>
* latest release: <https://github.com/OPMDG/check_pgactivity/releases/latest>
* contributors:
  <https://github.com/OPMDG/check_pgactivity/blob/master/contributors>

Thanks to all the contributors!

Reply via email to