On 13 May 2009, at 13:10, Andrew Hall 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 ?
Passive service checks usually require you to manually change the state back. However... I've just thought that we could have a servicecheck with a flag which is "reset state to OK after failure". So when an alert comes in, it goes through the state change including notifications and then we set a new state to change it back to OK automatically. This means the notification becomes the main method of finding out about these type of errors as the status view will show OK most of the time. This would require a change in the service checks page, a change in the configuration of the service to set this flag and a Nagios broker module to take affect if this flag is set on a service. Ton _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/listinfo/opsview-users
