create two different contacts with the same email address, one with a contact profile that alerts for critical messages 24x7, one with a profile that alerts warning messages 9-5, or whatever is appropriate.
On Wed, 10 Mar 2010 10:18:48 -0500, "Nicolas Ross" <[email protected]> wrote: > Hi ! > > We have a nagios 2.x installation that I plan to upgrade to 3.x soon... > > For some services, I'd like to be able to send notification 24x7, but only > with a critical state. For exemple a disk space checking service. When it > reaches warning state, I don't want to be waked up at 3 am. But when it's > critical, it's ok. > > I know I can define 2 services whith 2 notification_options and 2 time > periods, but that would make 2 services, with 2 different names for every > partition on our servers... > > Is there another way to acomplish this ? > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Nagios-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/nagios-users > ::: Please include Nagios version, plugin version (-v) and OS when > reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
