--On Wednesday, June 26, 2002 12:39 PM +0200 Laurent Combe
<[EMAIL PROTECTED]> wrote:
> with remote.monitor (v1.7)
> you can use arg called (--bigsummary)
>
> with the following output :
>
># --bigsummary : flag to extend the summary of this monitor
># return for each failed mon server the list of the
># failed. Like : host1([g1:s1{sum}|s3{sum}][g4:s5{sum}])
> ...
>
> where g1,g2,... are hostgroups
> where s1,s2,... are services
> and sum the summary
>
> does it help ?
> do you want i mail you directly this release ?
>
I think you misunderstood what I meant, maybe I wasn't clear.
My understanding of remote.monitor is that the "master" server would only
end up with a single hostgroup/service entry, and all the failure
information about the sub-servers would be in the summary for that single
entry. I want the "master" to have entries for every hostgroup/service
monitored by the sub-servers. That way if a service monitored by
sub-server A is actually dependent on a service monitored by sub-server B,
the master server can verify that dependency before sending an alert. Also
a client (like mon.cgi) can talk to just the master server, and get back
full status information rather then just a success/failure status bit for
the entire system (plus a summary containing the actual details). (And the
full status information, i.e. the FULL output from the failed montiors,
would be unavailable I think.)
Put another way, if I could call remote monitor and tell it precisely which
server/hostgroup/service to check, and just have it report based on the
status of that service, it would be closer to useful. But I still think
we'd lose the exit codes from the original monitor scripts, but maybe there
is a way to get those. I haven't actually used remote.monitor, I've just
looked at what the (sparse) documentation says it does.
-David
David Nolan <*> [EMAIL PROTECTED]
curses: May you be forced to grep the termcap of an unclean yacc while
a herd of rogue emacs fsck your troff and vgrind your pathalias!
