Greg (or anyone out there) ... have you had any experience with using
check_postgres.pl --action=dbstats with Cacti? I'm getting, in my
cacti.log, a result of:
SPINE: Poller[0] Host[124] DS[2619] SCRIPT:
/usr/local/bin/check_postgres.pl --action=dbstats --host=192.0.2.23
--dbuser=monitor
Found it ... spine (the new poller for cacti) doesnt' seem to report
errors very well ... switched to cmd.php and it turns out that, low and
behold, it can't find psql since /usr/local/bin isn't part of the path ...
fixed that in check_postgres.pl and all works well now ...
On Wed, 3 Mar
First, thanks for the pointer to the Check_postgres stuff, definitely alot
of good stuff in there ... but ... that is a totally different beast then
I'm looking at from Cacti (or, so I believe) ... for instance,
Check_posgres:database_size will alert me if I go over X size, which is
useful
Greg, before I start hacking away at it, do you have any examples of using
check_postgres_dbstats with cacti? rather not recreate teh wheel is
someone has already done it ...
thx ...
On Sat, 27 Feb 2010, Greg Smith wrote:
Marc G. Fournier wrote:
We are mainly a nagios / cacti
On Mon, 2010-03-01 at 14:43 -0400, Marc G. Fournier wrote:
First, thanks for the pointer to the Check_postgres stuff, definitely alot
of good stuff in there ... but ... that is a totally different beast then
I'm looking at from Cacti (or, so I believe) ... for instance,
Marc G. Fournier wrote:
We are mainly a nagios / cacti environment, and I came across...
Why start with Cacti then? There's way more Nagios integration
available; the little check_pgsql that comes with it (I think it's still
there), and the whole list at
In one of my new roles, one of my projects has been to setup a proof of
concept solution using PostgreSQL, which one emphasis being on performance
monitoring during testing / dev ...
We are mainly a nagios / cacti environment, and I came across:
