[PATCH] Distinguish between warning and critical notifications

Hendrik Baecker andurin at process-zero.de
Wed Nov 18 07:16:51 CET 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 18.11.09 01:02, schrieb Mark Gius:
> 
> The patch adds 4 configuration directives to service escalations
> definitions:
> 
>    first_warning_notification #
>    last_warning_notification #
>    first_critical_notification #
>    last_critical_notification #
> 
> Behavior is identical to (first|last)_notification, except that they
> check against the count of warning/critical notifications instead of the
> number of total notifications.

Hi,

I really like this but what about unknown state notifications which
might be used?

What about hostescalations? Would you patch them too?

- -
Hendrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAksDkVMACgkQlI0PwfxLQjnEBACbBFQAp6KoCASZzkg72BQ2+C/M
VdMAn1rT80v4EzBvknTDnC2yw9NPymAW
=CNI8
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july




More information about the Developers mailing list