[check_postgres] perfdata output
Cédric Villemain
cedric.villemain at dalibo.com
Fri Feb 20 13:38:41 UTC 2009
Hello
I'd like to have a perfdata output which is 'consistent'. Using Nagios, we
generate graph with pnp4nagios, but the pain is that check_postgres doesn't
output everytime the same things in the perfata and pnp4nagios loose (because
it lacks one DS or get one extra).
In order to filter out those issues, I think the better way is to use the --
include.
So I propose the following thing : --include also define the order and minimum
information given after the | (so the perfdata as undertsood by nagios)
./check_postgres.pl --action backends --include="foo,bar"
POSTGRES_BACKENDS OK: 0 of 100 connections (0%) | time=0.05 foo=0 bar=0
./check_postgres.pl --action backends --include="bar,foo"
POSTGRES_BACKENDS OK: 5 of 100 connections (5%) | time=0.05 bar=5 foo=0
./check_postgres.pl --action backends --include="bar,foo"
POSTGRES_BACKENDS OK: 13 of 100 connections (13%) | time=0.05 bar=5 foo=0
test=8
./check_postgres.pl --action backends
POSTGRES_BACKENDS OK: 0 of 100 connections (0%) | time=0.05
Do you like the idea ?
----
Cédric Villemain
Administrateur de Base de Données
Cel: +33 (0)6 74 15 56 53
http://dalibo.com - http://dalibo.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://mail.endcrypt.com/pipermail/check_postgres/attachments/20090220/f6f8d705/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : https://mail.endcrypt.com/pipermail/check_postgres/attachments/20090220/f6f8d705/attachment.bin
More information about the Check_postgres
mailing list