Re: {bb} Enhancement to user defined routines.

[Chuck Duerson <chuck@duerson.com>]

I'll try that and let you know how it goes.  Thanks for the input..

On Sat, 29 May 1999, Robert-Andre Croteau wrote:

> Chuck Duerson wrote:
> > 
> > On Sat, 27 Mar 1999, Robert-Andre Croteau wrote:
> > 
> > > Chuck Duerson wrote:
> > > >
> > > > First I would like to say that the addition of the ext directory for user
> > > > defined check routines has been a life saver.
> > > >
> > (snip)
> > > >
> > >
> > > Chuck,
> > >
> > > refresh my memory about your problem (we have discussed it a bit on
> > > the #bb1984 undernet channel).  IS it because you have too many
> > > summary entries ?  If so maybe wrapping them like the dialup wouldn't
> > > be a bad idea.  If not, then maybe you should merge some of your columns
> > > into a single or fewer columns. Continuing regular columns on the next
> > > line creates another problem on how to deal with the column names :(
> > > unless you group all hosts with those tests with a group-compress
> > > directive.
> > >
> > >
> > I need to be able to monitor several (10 or so) processes. This would
> > definately cause the line to wrap.
> > 
> > I could combine all the user test routines in one but I need to build a
> > page for the users to look at to check on the status of other systems so
> > they can send customers to those sites if there are problems at there
> > location. For this reason I need separate logs for each test.
> > 
> > My thought was that if you added some keyword like ext1 ext2 etc. that
> > when you built the page you could put the ext1.MACHINE under the MACHINE
> > and then drop the ext keyword and you would be left with the MACHINE.test.
> > The user could then control where there data displyed.  This would also
> > (possibly) eliminate the need for implementing a line wrap routine.
> > 
> > I hope this cleared it up a bit.
> 
> I'm easily confused today :)
> 
> I guess that all tests are run under the ext directory, right ?
> 
> Instead of sending a message with a regular bb hostname ($MACHINE):
> 
> $BB $BBDISP status $MACHINE.mytest1 $COLOR `date` - ....
> $BB $BBDISP status $MACHINE.mytest2 $COLOR `date` - ....
> 
> Why don't you send for those test something along the lines:
> 
> $BB $BBDISP status bb-$MACHINE.mytest1 $COLOR `date` - ....
> $BB $BBDISP status bb-$MACHINE.mytest2 $COLOR `date` - ....
> 
> and then in the bb-hosts, all hosts that run those tests could have
> their regular entry but you could create a group with just those
> tests:
> 
> #regular entries
> 123.123.123.123 host1	# ftp smtp
> 124.124.124.124 host2	# ftp smtp
> 125.125.125.125 host3	# ftp smtp
> 
> # Special procs entries
> group-compress <H3>Special Chuck tests</H3>
> 123.123.123.123 bb-host1	# noping
> 124.124.124.124 bb-host2	# noping
> 125.125.125.125 bb-host3	# noping
> 
> noping because you've already tested with the regular name.
> 
> The bb-host[123] will match in bb-hosts and they'll all
> be together with only columns of your special tests.
> 
> BTW, don't forget to add in bbwarnsetup.cfg all the error code ids
> matching your special tests.  add entries to the svcerrlist:
> test1:901 test2:902 test3:903 ....
> 
> my 2cents,
> 
> bye
> -- 
> Robert-Andre Croteau	BSD,MOTU		robert@unix.sh
> Services Conseils Informatiques MOTU Inc. 	robert@motu.ca
> (514) 465-3057					rcroteau@videotron.ca
> http://www.motu.ca/                             http://www.bb4.com
> 	Si le bonheur ne s'achete pas alors louez le.
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   Please send mail for the mailing list to: bb@taex001.tamu.edu
>   To [un]subscribe to this list, send e-mail to majordomo@taex001.tamu.edu
>      with [un]subscribe bb in the BODY of the message.
>   Please contact the mailing-list-owner as: bb-owner@taex001.tamu.edu
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  Please send mail for the mailing list to: bb@taex001.tamu.edu
  To [un]subscribe to this list, send e-mail to majordomo@taex001.tamu.edu
     with [un]subscribe bb in the BODY of the message.
  Please contact the mailing-list-owner as: bb-owner@taex001.tamu.edu