On 10/17/07, Jacques Klein <[EMAIL PROTECTED]> wrote:
> Well, not really, or not enough in fact.
> If I understand the "depend", it's a way to avoid multiple alerts by
> specifying dependencies between services in ONE mon.
> If I take this concept, then it would have to be extended to
> dependencies between services in a GROUP of mon(s) (one per host)....,
> interesting.... but seems very complicated.
>
If you configure each of your mon servers to send traps to all of the
others on status updates, then you can use dependencies on each server
based on state changes from other servers.
If they're all one one LAN you could probably even do that by sending
the status updates as broadcast packets. I've never tried that, it
might take minor coding in Mon to make it process broadcast packets.
Of course even better would be multicast, but that would definitely
require some code changes.
The best way to cause all status updates to get propagated is by using
the 'redistribute' config option. From the manual:
redistribute alert [arg...]
A service may have one redistribute option, which is a special
form of an an alert definition. This alert will be called on
every service status update, even sequential success status
updates. This can be used to integrate Mon with another moni-
toring system, or to link together multiple Mon servers via an
alert script that generates Mon traps. See the "ALERT PROGRAMS"
section above for a list of the parameters mon will pass auto-
matically to alert programs.
Combine redistribute with trap.alert, define all your watches and
services on all servers, and then you can do lots of stuff with
dependencies.
-David
_______________________________________________
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
