granular notifications

[Terry]

Good idea on the script.  However, I think you're right about the
multiple contacts.

On Tue, Nov 3, 2009 at 12:02 PM, Martin Melin <mmelin at gmail.com> wrote:
> If your notification command sorts out whether to page or email, why not
> have it handle empty pager addresses? Just remove the pager address from the
> contacts that shouldn't get pages, and you should be fine.
>
> However I usually like and recommend separate contacts, one per contact
> method, as this allows you to be more flexible in setting up escalation
> chains etc. as well as removing ambiguity as to how a contact was notified.
>
> Regards,
> Martin Melin
>
> On Tue, Nov 3, 2009 at 6:06 PM, Terry <td3201 at gmail.com> wrote:
>>
>> Sorry for the bad subject.  Not sure how to classify this properly.
>>
>> I have a single contact definition for each contact:
>>
>> define contact{
>>        contact_name                    jo at hotmail.com
>>        alias                           John Doe
>>        service_notification_period     24x7
>>        host_notification_period        24x7
>>        service_notification_options    w,u,c,r
>>        host_notification_options       d,u,r
>>        service_notification_commands   notification-wrapper-service
>>        host_notification_commands      notification-wrapper-host
>>        email                           jo at hotmail.com
>>        pager                           1231231234 at vtext.com
>>        can_submit_commands             1
>>        }
>>
>>
>> This works pretty well.  The command sorts out whether to page or to
>> email, however, in the event I want to disable pages only for this
>> contact, I can't figure out how to do it without separate contacts
>> like this:
>>
>> define contact{
>>        contact_name                   jdoe-email
>>        alias                           jdoe-email
>>        service_notification_period     24x7
>>        host_notification_period        24x7
>>        service_notification_options    w,u,c,r
>>        host_notification_options       d,u,r
>>        service_notification_commands   notify-by-email
>>        host_notification_commands      host-notify-by-email
>>        email                           jo at hotmail.com
>>        }
>>
>> define contact{
>>        contact_name                    jdoe-epager
>>        alias                           jdoe-epager
>>        service_notification_period     none
>>        host_notification_period        none
>>        service_notification_options    c,r
>>        host_notification_options       d,r
>>        service_notification_commands   notify-by-epager
>>        host_notification_commands      host-notify-by-epager
>>        email                           1231231234 at vtext.com
>>        }
>>
>> With the above, I can simply set the notification period to none and
>> thus pages are disabled.   Can anyone think of another way to do this,
>> other than timeperiods?   Keep in mind, that I still may want critical
>> emails, just not pages.
>>
>> Thanks!
>>
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>> is the only developer event you need to attend this year. Jumpstart your
>> developing skills, take BlackBerry mobile applications to market and stay
>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>> http://p.sf.net/sfu/devconference
>> _______________________________________________
>> Nagios-users mailing list
>> Nagios-users at 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
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Nagios-users mailing list
Nagios-users at 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