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 --dbpass=monitor --dbname=test, output: U
The specific problem bing the 'output: U', which should look something
like:
output: backends:1 commits:97645 rollbacks:5 read:177034 hit:6872718
idxscan:0 idxtupread:0 idxtupfetch:0 idxblksread:2199 idxblkshit:3
seqscan:3 seqtupread:1000110 ret:24845129 fetch:2956289 ins:2201738
upd:3999 del:312 dbname:test
Google seems to have a bunch of stuff talking about 'output: U', but
dating back to '06 and older ... the command runs fine (and fast) from the
command line, so not a timeout ...
So, anyone using dbstats with the newest version of Cacti, and have it
working?
On Mon, 1 Mar 2010, Marc G. Fournier wrote:
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 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
http://exchange.nagios.org/directory/Plugins/Databases/PostgresQL
I'd think that starting with http://bucardo.org/wiki/Check_postgres for
example would put you way ahead of anything that's available for Cacti.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@xxxxxxxxxxxxxxx www.2ndQuadrant.us
----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scrappy@xxxxxxx http://www.hub.org
Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@xxxxxxx
----
Marc G. Fournier Hub.Org Hosting Solutions S.A.
scrappy@xxxxxxx http://www.hub.org
Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@xxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general