The idea was to only use it for notifications only. In a reasonably
funcional environment notifications should'nt be sent often enough to
become a performance killer should they?
/M=20
-----Original Message-----
From: Andreas Ericsson [mailto:[email protected]]=20
Sent: den 21 november 2008 16:34
To: Nagios Developers List
Subject: Re: [Nagios-devel] Command to replace timeperiod
[email protected] wrote:
> I've been considering implementing the use of "standard" Nagios=20
> commands to make it possible to incorporate any kind of calendar
functionality.
>=20
> Hosts and services could have an option=20
> "notification_timeperiod_commands" or something like that.
>=20
> Good or bad idea?
>=20
Bad. It's a performance killer for anything but very small environments,
as timeperiods are checked every time a check is run, or a notification
is sent, or a check is rescheduled, or... etc.
If you need something like this, submit a patch to let NEB-modules
replace the timeperiod functionality and then let that NEB-module check
things up in a database/external file/whatever.
--=20
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge Build the coolest Linux based applications with Moblin SDK &
win great prizes Grand prize is a trip for two to an Open Source event
anywhere in the world
http://moblin-contest.org/redirect.php? ... 00&url=3D/
_______________________________________________
Nagios-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/lis ... gios-devel
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: ndreas Ericsson [mailto:[email protected]]=2