Same contact - two different notification methods

[Peter Wood]

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 user1 at company.com
  }

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20130521/0494dc27/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
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
-------------- next part --------------
_______________________________________________
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