On 10/5/07, Aidan Anderson <[EMAIL PROTECTED]> wrote: > Terry wrote: > > Thanks for the reply. Let me be more specific: > > > > version: 2.9 > > OS: centos 5 > > > > I have regular contacts set up, me for example. I want to get > > notified every 30 minutes indefinitely if a service is in a hard state > > of warning or critical. However, I want another contact to only get > > notified one time when that hard state is achieved. That's it. > > >From what I can tell, I can only achieve this through the > > notification_interval which is only set at the host/service level, not > > the contact level. If this is true, I will need to create 2 services, > > each with a different notification_interval and of course apply the > > different contact groups to each service. Am I correct or is there > > another way around this? > > > > Thanks! > > > > On 10/5/07, Aidan Anderson <[EMAIL PROTECTED]> wrote: > > > >> Terry wrote: > >> > >>> I have a contact that I only want to receive one notification. How > >>> can I set this up? > >>> > >>> > >>> > Hi Terry, > > I've just posted you another message before seeing this one. You want > to use host or service escalations to achieve this. I've briefly > explained in the previous post but if you need more help, just shout. > > Aidan >
Thanks for your reply. It looks like for me to achieve this, I will need to create 2 escalations for every service. One for the single notification and the other for standard notifications. That seems like a lot of configuration. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
