[check_postgres] [PATCH] Add `pgagent_jobs` test.

[Cédric Villemain]

Le 18 janvier 2012 23:44, David E. Wheeler <david at justatheory.com> a écrit :
> On Jan 18, 2012, at 2:42 PM, David E. Wheeler wrote:
>
>> This patch adds support for checking for failed pgAgent jobs within a specified period of time. You can specify either --critical or --warning as a period of time, and it will report on failures within that period of time previous to the current time. Job failures are determined by a non-0 status in a job step record.
>>
>> Using this test obviously requiers that the pgAgent schema be installed. I've also included a bunch of unit tests to make sure it works the way I would expect (the test will create a schema for testing) and documentation.
>>
>> As part of this, I've introduced the `any_warning` argument to `validate_range()`. The `pgagent_jobs` test does not care if you specify a warning value greater than the critical value (indeed, I expect that if one used both at all, the warning would be much longer). So this new argument prevents the `range-warnbigtime` or `range-warnbigsize` failures from being triggered.
>
> Assuming everyone is on board with this, I can commit it. Just let me know.

I didn't understand this any_warning. What is it for again ?
I believe, all check_postgres need is sometime more in line with
nagios plugin guidelines, not the opposite.
I'll check further, but I would like you to see my mail before committing ;)

>
> Thanks,
>
> David
>
> _______________________________________________
> Check_postgres mailing list
> Check_postgres at bucardo.org
> https://mail.endcrypt.com/mailman/listinfo/check_postgres



-- 
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation