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. Are you testing in a distributed setup using Notify By SMS only? Thanks, James Whittington VC3, Inc. From: [email protected] [mailto:[email protected]] On Behalf Of Ton Voon Sent: Friday, March 05, 2010 11:25 AM To: Opsview Users Subject: Re: [opsview-users] Bug in Opsview Escalations using SMS method On 5 Mar 2010, at 14:36, James Whittington wrote: Ton, That didn't seem to work. Looking back at your email, you're specifically mentioning escalations, so it is not the same problem I was expecting. Which version of Opsview works and which one doesn't? I've just done a test of a new service and I got an escalation email on the 1st alert for one contact, and on the 2nd alert for a different contact as expected. Is it possible you have a service that is already in a failed state and already notifying (and hence the notification level is already > 3). Ton
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
