On 26 Mar 2010, at 07:56, Jacob d'Andrade wrote:

I’m having problems with a contact, where there should be sent a sms message, but Ospview sends an email instead, allthoug there isn’t an email address specified for that contact…

Contact config:

# 'Jacob - SMS' contact definition
define contact {
        contact_name    admin-jd-sms/masterprofile
        alias           Jacob - SMS
        use             global-contact
        service_notification_period     24x7
        host_notification_period        24x7
        notification_level              1
contactgroups A LOOOOOOT OF CONTACTGROUPS – REMOVED TO SIMPILIFY HERE… pager 004512345678 (REPLACED WITH FAKE CELL PHONE NUMBER HERE)
        host_notification_commands      notify-by-foxbox
        host_notification_options       d,r
        service_notification_commands   notify-by-foxbox
        service_notification_options    w,c,r,u,f
}


I have reloaded the configuration and tried a reboot of the Opsview server, but still Opsview thinks it should contact my sms contact by email? I have a custom sms script, the command is simplified until I get it to work…

define command{
        command_name notify-by-foxbox
command_line /usr/local/nagios/libexec/notifications/ foxbox.sh $CONTACTPAGER$ $HOSTNAME$
}

I have the same script running on a normal Nagios installation where the messages work perfect, why does Opsview send the message via service-notify-by-email instead of notify-by-foxbox ?

Nagios.log:
[1269589324] SERVICE NOTIFICATION: admin-jd-sms;asf- core;Connectivity - LAN;CUSTOM (OK);service-notify-by-email;OK - asf- core: rta 1.318ms, lost 0%;Jacob;Testing

Can anyone tell me why this is happening?

The admin-jd-sms in the nagios.log is not the same as the contact above. The contact above is called admin-jd-sms/masterprofile. What is the definition for admin-jd-sms?

In a distributed environment, we use multiple contacts in order to differentiate between what is notified on the master and what is notified from the active monitoring server. We've got a much more elegant solution in 3.7.0.

Ton

_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users

Reply via email to