We're working on sending some custom traps from our internal software here and one of the requirements I placed on our devs is that they send "all clear" type traps, either via a heartbeat type mechanism.
On Wed, May 13, 2009 at 7:10 AM, Andrew Hall <[email protected]>wrote: > I really would be very interested to hear from others how they deal > with this quandary. > > To simplify... > > 1. A trap sets a service to a critical state. > > 2. There is no equivalent trap to set that state to OK. > > 3. The issue is resolved. > > 4. How do you now return the service state to OK ? > > Surely there must be others passing traps to Opsview who have had to > deal with this ? > > Thanks very much. > _______________________________________________ > Opsview-users mailing list > [email protected] > http://lists.opsview.org/listinfo/opsview-users > -- Ben Lutgens Linux / Unix System Administror Three of your friends throw up after eating chicken salad. Do you think: "I should find more robust friends" or "we should check that refrigerator"? -- Donald Becker, on vortex-bug, suspecting a network-wide problem
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/listinfo/opsview-users
