check_postgres.pl - a Postgres monitoring script for Nagios, MRTG, Cacti, and others
-This documents describes check_postgres.pl version 2.15.0
+This documents describes check_postgres.pl version 2.15.1
Allows specification of the method used to fetch information for the new_version_cp,
-new_version_pg, and new_version_bc checks. The following programs are tried, in order, to
-grab the information from the web: GET, wget, fetch, curl, lynx, links. To force the use of just
+new_version_pg, new_version_bc, and new_version_tnm checks. The following programs are tried,
+in order, to grab the information from the web: GET, wget, fetch, curl, lynx, links. To force the use of just
one (and thus remove the overhead of trying all the others until one of those works),
enter one of the names as the argument to get_method. For example, a BSD box might enter
the following line in their .check_postgresrc file:
+
(symlink: check_postgres_new_version_bc) Checks if a newer version of the Bucardo
+program is available. The current version is obtained by running bucardo_ctl --version.
+If a major upgrade is available, a warning is returned. If a revision upgrade is
+available, a critical is returned. (Bucardo is a master to slave, and master to master
+replication system for Postgres: see http://bucardo.org for more information).
+See also the information on the --get_method option.
+
(symlink: check_postgres_new_version_cp) Checks if a newer version of this program
(check_postgres.pl) is available, by grabbing the version from a small text file
@@ -956,12 +975,13 @@ It is recommended this check is run at least once a day. See also the informatio
the --get_method option.
-
(symlink: check_postgres_new_version_bc) Checks if a newer version of the Bucardo
-program is available. The current version is obtained by running bucardo_ctl --version.
-If a major upgrade is available, a warning is returned. If a revision upgrade is
-available, a critical is returned. (Bucardo is a master to slave, and master to master
-replication system for Postgres: see http://bucardo.org for more information).
+
(symlink: check_postgres_new_version_tnm) Checks if a newer version of the
+tail_n_mail program is available. The current version is obtained by running
+tail_n_mail --version. If a major upgrade is available, a warning is returned. If a
+revision upgrade is available, a critical is returned. (tail_n_mail is a log monitoring
+tool that can send mail when interesting events appear in your Postgres logs.
+See: http://bucardo.org/wiki/Tail_n_mail for more information).
See also the information on the --get_method option.
@@ -986,6 +1006,46 @@ checksum must be provided as the
--mrtg argument. The fourth line a
current checksum.
+
+
++
++
++
++
++
++
+(symlinks: check_postgres_pgb_pool_cl_active, check_postgres_pgb_pool_cl_waiting,
+check_postgres_pgb_pool_sv_active, check_postgres_pgb_pool_sv_idle,
+check_postgres_pgb_pool_sv_used, check_postgres_pgb_pool_sv_tested,
+check_postgres_pgb_pool_sv_login, and check_postgres_pgb_pool_maxwait)
Examines pgbouncer's pool statistics. Each pool has a set of "client" +connections, referring to connections from external clients, and "server" +connections, referring to connections to PostgreSQL itself. The related +check_postgres actions are prefixed by "cl_" and "sv_", respectively. Active +client connections are those connections currently linked with an active server +connection. Client connections may also be "waiting", meaning they have not yet +been allocated a server connection. Server connections are "active" (linked to +a client), "idle" (standing by for a client connection to link with), "used" +(just unlinked from a client, and not yet returned to the idle pool), "tested" +(currently being tested) and "login" (in the process of logging in). The +maxwait value shows how long in seconds the oldest waiting client connection +has been waiting.
++
(symlink: check_postgres_prepared_txns) Check on the age of any existing prepared transactions.
Note that most people will NOT use prepared transactions, as they are part of two-part commit
@@ -1306,6 +1366,23 @@ out of space, at which point Postgres will shut down.
For MRTG output, reports the number of WAL files on line 1.
+
(symlink: check_postgres_archive_ready) Checks how many WAL files with extension .ready
+exist in the pg_xlog/archive_status directory, which is found
+off of your data_directory. This action must be run as a superuser, in order to access the
+contents of the pg_xlog/archive_status directory. The minimum version to use this action is
+Postgres 8.1. The --warning and --critical options are simply the number of
+.ready files in the pg_xlog/archive_status directory.
+Usually, these values should be low, turning on the archive mechanism, we usually want it to
+archive WAL files as fast as possible.
If the archive command fail, number of WAL in your pg_xlog directory will grow until +exhausting all the disk space and force PostgreSQL to stop immediatly.
+Example 1: Check that the number of ready WAL files is 10 or less on host "pluto"
++ check_postgres_archive_ready --host=pluto --critical=10+
For MRTG output, reports the number of ready WAL files on line 1.
++
(symlink: check_postgres_version) Checks that the required version of Postgres is running. The
--warning and --critical options (only one is required) must be of
@@ -1490,10 +1567,17 @@ feature requests, and commit notices, send email to HISTORY
Items not specifically attributed are by Greg Sabino Mullane.
+ Fix problem when examining items in pg_settings (Greg Sabino Mullane)+
+ Add --quiet argument to surpress output on OK Nagios results
Add index comparison for same_schema (Norman Yamada and Greg Sabino Mullane)
Use $ENV{PGSERVICE} instead of "service=" to prevent problems (Guillaume Lelarge)
Add --man option to show the entire manual. (Andy Lester)
@@ -1505,7 +1589,10 @@ feature requests, and commit notices, send email to Version 2.14.3 (March 1, 2010)
--
cgit v1.2.3