As a side note to this conversation, we do our configuration a wee bit differently.
We require the ability to get stats, disable services and get alerts specific to each host. Basically, we need everything to happen at the host level. In order to accomplish this, we map one host group to one host. The bonus to this configuration is that we always know specifically which service on which host is down when we receive a page. The pages we get look like $host/$server - $short_summary\n$date. If http on server a fails, we get one page plus pages every X minutes. If server b's http fails, we get one page plus pages every X minutes. The negatives, of course, are that we have a lot of perl forks happening on our monitoring servers. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of David Nolan > Sent: Tuesday, November 23, 2004 7:31 AM > To: mon_list > Subject: Re: alerts functionality > > > > --On Monday, November 22, 2004 1:45 PM -0500 Jim Trocki > <[EMAIL PROTECTED]> wrote: > > >> so total alerts sent is 1+2+3...+10? > >> > >> is the latter correct? I've only tested it up to two hosts going down > >> consecutively :) > > > > it's correct depending on how you configure mon. this is the default > > behavior, but you can change it. > > Also, it should be pointed out that this is entirely dependent on the > behavior of the monitor script. If the script outputs a different > summary, > then Mon will alert again (unless configured not to). Most scripts output > the list of failing hosts as the summary, but not all. > > -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! > > _______________________________________________ > mon mailing list > [EMAIL PROTECTED] > http://linux.kernel.org/mailman/listinfo/mon _______________________________________________ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
