Re: Same contact - two different notification methods

Thanks Steve.

It would have been nice if I can define
[host|service]_notification_commands in the service definition. This way
one can create notify-by-pager command that will use the pager directive in
the contact definition.

Feature request I guess.

-- Peter

On Tue, May 21, 2013 at 2:10 PM, Steven Carr <[email protected]> wrote:

> Yes, you create separate contacts. AFAIK there is no way to
> distinguish which alert method you want to use, so unless the user
> wants to be SMS'd about every notification you need to separate them
> out.
>
>
> On 21 May 2013 21:49, Peter Wood <[email protected]> wrote:
> > Hi,
> >
> > I have two services monitoring http on two servers:
> >   http on server1 - Email notifications
> >   http on server2 - Email + SMS notifications
> >
> > Http on server1 is not critical and notifications should go out via
> email.
> > Http on server2 is critical and notifications should go out via email and
> > SMS.
> >
> > The only place where I can setup how an user should be contacted is in
> the
> > contact definition.
> >
> > Does that mean I have to create two contact definitions for each user:
> one
> > for email notifications and one for sms notifications?
> >
> > For example:
> >
> > define contact {
> >   contact_name user1
> >   ...
> >   email [email protected]
> >   }
> >
> > define contact {
> >   contact_name user1-sms
> >   ...
> >   email <phone number>@txt.att.net  ; I have AT&T but it can be any
> other
> > email-to-sms service
> > }
> >
> > define service {
> >   host_name server1
> >   ...
> >   contacts user1
> > }
> >
> > define service {
> >   host_name server2
> >   ...
> >   contacts user1-sms
> > }
> >
> > Am I missing something? Is there a way to do it without creating two
> contact
> > definitions for the same user?
> >
> > Thanks,
> >
> > -- Peter
> >
> >
> ------------------------------------------------------------------------------
> > Try New Relic Now & We'll Send You this Cool Shirt
> > New Relic is the only SaaS-based application performance monitoring
> service
> > that delivers powerful full stack analytics. Optimize and monitor your
> > browser, app, & servers with just a few lines of code. Try New Relic
> > and get this awesome Nerd Life shirt!
> http://p.sf.net/sfu/newrelic_d2d_may
> > _______________________________________________
> > 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
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> 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
>

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may

_______________________________________________
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