Re: {bb} Re: Paging

[Scott Walters <scott@PacketPushers.com>]

i am finding the follwing rules are not behaving as i think they should

# at night, for prod machines, we only want to be reminded every two
# hours,
# after it's been down for ten minutes
*;;*;;*;0000-0600 1800-2359;*:^10-120

# our trusty admins
*;;*;;*;*;scott@mysite.com:60


it is matching witht he scond rule and sending eamil every hour, ugh.  at
first glance it seems the wildcard in the recipient line doesn't precede
an exact match . . . 

BIG THOUGHT
***********

since BBPAGER is only *one* machine why not write the bb-page stuff in
perl?  i understand the motivation for all the clients to run on every
incarnation of UNIX known to man, but i bet the majority of brothers have
perl on their BBPAGER machine.  

just seems perl would be a much better fit for all the stuff the paging
needs to do.  imagine being able to use arrays and hashes  . . . 

the below has been sitting in my buffer for a week, i can't remmber what
it was really about . . . just more observations . . .  

On Wed, 25 Aug 1999, Robert-Andre Croteau wrote:

> > so if:
> > 
> > pagelevels: red yellow purple
> > pagelevelsmail: red yellow purple
> > 
> > then *only* emails will ever be sent out?
> 
> yup

I am not seeing that behavior.  email is being sent out for all events,
even if a page is sent as well.

I looked at bb-page1.sh and I can't make much sense of the two nested
'case $page' statements under the 'case $BBCOLORLEVEL' command at the end.

1)  why is the second case statement, which dictates pages being sent, in
a case command cycling through the $PAGELEVELSMAIL and not $PAGELEVELS?

2)  why is there a *@* in the second nested 'case $page'?  isn't the
decision to send an email in the preceding case command?

Personally I feel an email should *always* be sent (when matching
recipients are found) if a page is sent. so perhaps the docs in
bbwarnsetup.cfg hasn't caught up with the code in bb-page1.sh

so i guess i would be interested in a $NOTIFYLEVEL (kinda currently
$PAGELEVELS) that would tell bb-page or bb-page1 to either A)  process the
event for notification or B) drop the event with no notifies

if A) is met then let bb-warnrules.cfg do the right thing

# send an email and page
*;;*;;*;*;root@localhost 555-5555

# just page
*;;*;;*;*;555-5556

> > > for now yes :(  It will change when I get time to revamp the whole
> > > notification
> > > structure ...

i would really like to now what your plans are with this.  would you care
to elaborate the 'revamp'?


> well, I have many clients who only have 56Kbs Frame Relay lines between
> sites.  Any reduction in network traffic is good ...
> 
> Also, each message will start up a bb-page.sh exec.  That's the
> resources
> I was talking about...

maintanance/admin has an overhead . . .   

> Well, it's in the cards for the next release so I'll see what I can do
> but
> I sure would like to get rid of the etc/bbwarnsetup.cfg on the clients.

agreed.

also, this doesn't seem to work right:
!hg-test;;*;;*;1800-0600;*

do you have to restrict it like this?:
!hg-test;;*;;*;0000-0600 1800-2359;*

just tested the above and it works. . . . . 

--
Scott Walters
-PacketPusher

"The world speaks IP"


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.