At 09:42 AM 11/21/01 -0500, [EMAIL PROTECTED] wrote: > I >guess the right way to handle this would be to keep a list within mon of >current failure states that haven't gone back to zero, and send upalerts to >all of them? > >I realize it would probably be a lot of work to hack this into mon, but it >would be a really useful feature.
It's the right direction, but it's still not a complete solution without host awareness. For example, to extend your example, not only is it possible for exit statuses to change each time a monitor is run, but it's also possible for the failed hosts to change, and for different hosts to have different exit statuses. So not only would you need to match up exit codes but also hosts. Doing this in the current 0.99 codebase would be possible, but probably a huge and ugly hack. I think we'll have to wait for the 1.1 development branch when Jim revamps some of the protocols to allow for more fine-grained alerting, to leverage the scalability of the hostgroup concept and still allow for very fine-grained state tracking at the per-host and per-service level.
