Re: [opsview-users] Bug in Opsview Escalations using SMS method

[Ton Voon]

On 5 Mar 2010, at 18:02, James Whittington wrote: Ton in 2 cases I have seen escalations work with Ospview and in both of those cases it was a master server only model. I track notification number in the notification so these are not pre-existing conditions being alerted on. Key items of interest: I have observed the issue on 2 different Opsview systems now, both are distributed models, one being the reverse ssh model and the other being direct ssh model. Both systems are 3.5 and were recently upgraded, but the issue occurred on both systems on an earlier 3.x version of Opsview as well. Both Distributed systems call a custom SMS method that is run from the master server. The contacts only have “notify by sms” checked.   I suspect the issue may have been around a while but you would have to do escalations in a distributed model using Notify By SMS only. This extra details helps. Try the patch attached. I think the problem is that we missed off the notification_level attribute for the contact definition where the check is done on the slave but the notification is set to master only. Ton

notifications.patch
Description: Binary data

_______________________________________________
Opsview-users mailing list
Opsview-users@lists.opsview.org
http://lists.opsview.org/lists/listinfo/opsview-users