Xymon Mailing List Archive search

ACK with Delay

12 messages in this thread

list Asif Iqbal · Fri, 11 Feb 2005 14:00:04 -0500 ·
How do you send an ACK with Delay through the email in Hobbit?

Should I need to use BB commands? Does it generate any ACK Code that I
can associate with BB command to delay?

Thanks for the help

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
"...it said: Install Windows XP or better...so I installed Solaris..."
list Henrik Størner · Fri, 11 Feb 2005 22:24:37 +0100 ·
quoted from Asif Iqbal
On Fri, Feb 11, 2005 at 02:00:04PM -0500, Asif Iqbal wrote:
How do you send an ACK with Delay through the email in Hobbit?

Should I need to use BB commands? Does it generate any ACK Code that I
can associate with BB command to delay?
Alerts do include an ACK code, also in Hobbit. I haven't tried it,
but since the BB ack protocol is also supported in Hobbit, the BB
ack-by-mail script should work fine in Hobbit.

If that fails, then it is pretty simple - you need some sort of
e.g. procmail script that calls the "bb" tool like this:

  bb ip.of.hobbit.server "hobbitdack ACKCODE MINUTES TEXT"


Regards,
Henrik
list Asif Iqbal · Sat, 12 Feb 2005 20:23:26 -0500 ·
quoted from Henrik Størner
On Fri, Feb 11, 2005 at 10:24:37PM, Henrik Stoerner wrote:
On Fri, Feb 11, 2005 at 02:00:04PM -0500, Asif Iqbal wrote:
How do you send an ACK with Delay through the email in Hobbit?

Should I need to use BB commands? Does it generate any ACK Code that I
can associate with BB command to delay?
Alerts do include an ACK code, also in Hobbit. I haven't tried it,
but since the BB ack protocol is also supported in Hobbit, the BB
ack-by-mail script should work fine in Hobbit.

If that fails, then it is pretty simple - you need some sort of
e.g. procmail script that calls the "bb" tool like this:

  bb ip.of.hobbit.server "hobbitdack ACKCODE MINUTES TEXT"
Is there a way to retrieve an alert based on the ACKCODE? In Bigbrother
1.9c I was using the following script "findhostsvc.sh ACKCODE"--that I
received from the bigbrother mailing list--to get
the details. (I know it is not always reliable but it worked for me)

$ cat findhostsvc.sh

#!/bin/sh
BBHOME=/export/home/bbro/bb
ackcode=$1
cd $BBHOME/tmp
np_file=`grep $ackcode np_* 2>/dev/null`
set bogus `echo $np_file`
shift  # get rid of bogus
# $2 has host.service combination
hostsvc=$2
echo $hostsvc


Thanks for any suggestion on this.
Regards,
Henrik
quoted from Asif Iqbal

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
"...it said: Install Windows XP or better...so I installed Solaris..."
list Henrik Størner · Sun, 13 Feb 2005 08:30:23 +0100 ·
quoted from Asif Iqbal
On Sat, Feb 12, 2005 at 08:23:26PM -0500, Asif Iqbal wrote:
Is there a way to retrieve an alert based on the ACKCODE?
[snip BB script that picks out hostname+service for an ack code]

I hope you don't mind my asking: Why ?

The only way you can get the ack-code is via an alert-message that
already includes the host+service name.

So I'd like to know what you're using this for, because I have a
suspicion that you're really trying to do something that ought to be
done in another way.


Regards,
Henrik
list Asif Iqbal · Sun, 13 Feb 2005 11:09:21 -0500 ·
quoted from Henrik Størner
On Sun, Feb 13, 2005 at 08:30:23AM, Henrik Stoerner wrote:
On Sat, Feb 12, 2005 at 08:23:26PM -0500, Asif Iqbal wrote:
Is there a way to retrieve an alert based on the ACKCODE?
[snip BB script that picks out hostname+service for an ack code]

I hope you don't mind my asking: Why ?
This way I can keep the delay script simple. I do not have to parse the
host.service info from the subject or body of the message. Plus with
skytel it looses the subject. So I just look for the [12345] code in the
email and just use that as a reference to pick up the host.service

Thanks
quoted from Henrik Størner
The only way you can get the ack-code is via an alert-message that
already includes the host+service name.

So I'd like to know what you're using this for, because I have a
suspicion that you're really trying to do something that ought to be
done in another way.


Regards,
Henrik

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
"...it said: Install Windows XP or better...so I installed Solaris..."
list Henrik Størner · Sun, 13 Feb 2005 23:50:51 +0100 ·
quoted from Asif Iqbal
On Sun, Feb 13, 2005 at 11:09:21AM -0500, Asif Iqbal wrote:
On Sun, Feb 13, 2005 at 08:30:23AM, Henrik Stoerner wrote:
On Sat, Feb 12, 2005 at 08:23:26PM -0500, Asif Iqbal wrote:
Is there a way to retrieve an alert based on the ACKCODE?
[snip BB script that picks out hostname+service for an ack code]

I hope you don't mind my asking: Why ?
This way I can keep the delay script simple. I do not have to parse the
host.service info from the subject or body of the message. Plus with
skytel it looses the subject. So I just look for the [12345] code in the
email and just use that as a reference to pick up the host.service
Well, I still don't understand what you're using it for - what does
your "delay" script do ?

But there is a way of doing what you want. Send a "hobbitdboard"
request to the server, and look for the output to contain the
ack-code in field 11 (separated by '|' chars). Like the following
awk-script does (substitute "12345" with the ack-code you want):

  ~hobbit/server/bin/bb 127.0.0.1 "hobbitdboard" | \
     awk -F '|' '$11 == "12345" {print $1 " " $2 }'


Regards,
Henrik
list Asif Iqbal · Sun, 13 Feb 2005 21:07:33 -0500 ·
quoted from Asif Iqbal
On Fri, Feb 11, 2005 at 10:24:37PM, Henrik Stoerner wrote:
On Fri, Feb 11, 2005 at 02:00:04PM -0500, Asif Iqbal wrote:
How do you send an ACK with Delay through the email in Hobbit?
Should I need to use BB commands? Does it generate any ACK Code that I
can associate with BB command to delay?
Alerts do include an ACK code, also in Hobbit. I haven't tried it,
but since the BB ack protocol is also supported in Hobbit, the BB
ack-by-mail script should work fine in Hobbit.

If that fails, then it is pretty simple - you need some sort of
e.g. procmail script that calls the "bb" tool like this:

  bb ip.of.hobbit.server "hobbitdack ACKCODE MINUTES TEXT"
Is the ACKCODE same for all recipients? I know in bigbrother it was
different for different reciepent so you can either delay it for all OR
delay it for specific reciepient

Thanks
quoted from Asif Iqbal
Regards,
Henrik

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
"...it said: Install Windows XP or better...so I installed Solaris..."
list Asif Iqbal · Sun, 13 Feb 2005 21:17:32 -0500 ·
quoted from Asif Iqbal
On Sun, Feb 13, 2005 at 09:07:33PM, Asif Iqbal wrote:
On Fri, Feb 11, 2005 at 10:24:37PM, Henrik Stoerner wrote:
On Fri, Feb 11, 2005 at 02:00:04PM -0500, Asif Iqbal wrote:
How do you send an ACK with Delay through the email in Hobbit?
Should I need to use BB commands? Does it generate any ACK Code that I
can associate with BB command to delay?
Alerts do include an ACK code, also in Hobbit. I haven't tried it,
but since the BB ack protocol is also supported in Hobbit, the BB
ack-by-mail script should work fine in Hobbit.
If that fails, then it is pretty simple - you need some sort of
e.g. procmail script that calls the "bb" tool like this:
  bb ip.of.hobbit.server "hobbitdack ACKCODE MINUTES TEXT"
Is the ACKCODE same for all recipients? I know in bigbrother it was
Looks like they are. I guess may be adding separate cookie code for
separate reciepient in next release ?! :P

Thanks
quoted from Asif Iqbal
different for different reciepent so you can either delay it for all OR
delay it for specific reciepient

Thanks
Regards,
Henrik
-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
"...it said: Install Windows XP or better...so I installed Solaris..."

-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
"...it said: Install Windows XP or better...so I installed Solaris..."
list Henrik Størner · Mon, 14 Feb 2005 07:44:05 +0100 ·
quoted from Asif Iqbal
On Sun, Feb 13, 2005 at 09:07:33PM -0500, Asif Iqbal wrote:
Is the ACKCODE same for all recipients? I know in bigbrother it was
different for different reciepent so you can either delay it for all OR
delay it for specific reciepient
They are the same for all recipients.


Henrik
list Brent Mccrackin · Mon, 14 Feb 2005 09:39:52 -0500 ·
I think the question was asking if the unique pager identifier is
available in Hobbit.

The ACKCODE in BB is made up of a 5-digit alert code and a 2-digit pager
code to identify who the alert was sent to.  The 5-digit alert code is
the same for all recipients of that alert.  The pager code would change
depending on the sequence that the matching rule was encountered in the
bb-warnrules configuration.  Replacing the provided pager code with a 99
in the ACK input would acknowledge the alert for all recipients (except
the escalation ones marked with ^).

Is this feature retained in Hobbit?

If not, how do we identify who acknowledged an alert?

A feature I'd like to see is the ability to allow an identified
acknowledge of an alert based on the two-digit code, that stops alerts
for all recipients except escalation recipients (those being the people
that need to be alerted if a downed service is not fixed after a
specific time period regardless of someone working on it).  This would
do away with the need for a '99' acknowledge to stop alerts for
everyone, and let the person responding to the alert work on fixing it
faster (at least until the escalation person starts asking for status
reports).

---
Brent B McCrackin
UNIX Systems Specialist - Bell Sympatico
user-04bba0146b8b@xymon.invalid   PH: XXX-XXX-XXXX
"Serenity through viciousness."
quoted from Henrik Størner
 

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: February 14, 2005 1:44 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] ACK with Delay


On Sun, Feb 13, 2005 at 09:07:33PM -0500, Asif Iqbal wrote:
Is the ACKCODE same for all recipients? I know in bigbrother it was
different for different reciepent so you can either delay it for all
OR
delay it for specific reciepient
They are the same for all recipients.


Henrik
list Henrik Størner · Mon, 14 Feb 2005 17:29:42 +0100 ·
quoted from Brent Mccrackin
On Mon, Feb 14, 2005 at 09:39:52AM -0500, user-04bba0146b8b@xymon.invalid wrote:
The ACKCODE in BB is made up of a 5-digit alert code and a 2-digit pager
code to identify who the alert was sent to.  The 5-digit alert code is
the same for all recipients of that alert.  The pager code would change
depending on the sequence that the matching rule was encountered in the
bb-warnrules configuration.  Replacing the provided pager code with a 99
in the ACK input would acknowledge the alert for all recipients (except
the escalation ones marked with ^).

Is this feature retained in Hobbit?
No. the acknowledgement cookie in Hobbit only identifies a
host+service. The same ack-cookie is sent to everyone who is alerted.

The main reason Hobbit does not generate unique cookies for each
recipient is that to do so, the core daemon (hobbitd) and the alert
module (hobbitd_alert) would have to be a lot more aware of each other
than they are now.

If not, how do we identify who acknowledged an alert?
Make sure you include that information in the ack message you provide
when ack'ing the alert.

I admit that this isn't something I've given much thought, because it
isn't a real problem for me. But I've just added a bit of code to the
bb-ack CGI, so if you have the acknowledgement web form in the secure
CGI directory (which is the default setup), then the username used to
login to the secure area will be included in the ack-message, and
shown on the status page.


If that is not good enough, then we'll have to discuss how to do it 
for the next release.


Regards,
Henrik
list Brent Mccrackin · Mon, 14 Feb 2005 11:42:17 -0500 ·
We use RIM pagers to receive our BB alerts.  This allows us to
acknowledge alerts by replying to the message, and the bb-mailack script
takes care of everything else - including using the ACK code to identify
the user that is performing the ACK.

Granted, using the email address could be worked into the script, but
everything that I have in place now uses the ACK code as generated by BB
with dependencies on the Pager ID in the code.  Not every alert comes in
through the web interface.


Would it be posisble to 'preconfigure' the pager codes?  Instead of
having Hobbit generate the codes based on position in the matched rules
list, define the ID codes in advance in the config files.  Then we
always know which ID belongs to which pager, regardless of how the rules
are built.
signature

---
Brent B McCrackin
UNIX Systems Specialist - Bell Sympatico
user-04bba0146b8b@xymon.invalid   PH: XXX-XXX-XXXX
"Serenity through viciousness."
 

-----Original Message-----

quoted from Henrik Størner
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: February 14, 2005 11:30 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] ACK with Delay


On Mon, Feb 14, 2005 at 09:39:52AM -0500, user-04bba0146b8b@xymon.invalid wrote:
The ACKCODE in BB is made up of a 5-digit alert code and a 2-digit
pager
code to identify who the alert was sent to.  The 5-digit alert code is
the same for all recipients of that alert.  The pager code would
change
depending on the sequence that the matching rule was encountered in
the
bb-warnrules configuration.  Replacing the provided pager code with a
99
in the ACK input would acknowledge the alert for all recipients
(except
the escalation ones marked with ^).

Is this feature retained in Hobbit?
No. the acknowledgement cookie in Hobbit only identifies a
host+service. The same ack-cookie is sent to everyone who is alerted.

The main reason Hobbit does not generate unique cookies for each
recipient is that to do so, the core daemon (hobbitd) and the alert
module (hobbitd_alert) would have to be a lot more aware of each other
than they are now.

If not, how do we identify who acknowledged an alert?
Make sure you include that information in the ack message you provide
when ack'ing the alert.

I admit that this isn't something I've given much thought, because it
isn't a real problem for me. But I've just added a bit of code to the
bb-ack CGI, so if you have the acknowledgement web form in the secure
CGI directory (which is the default setup), then the username used to
login to the secure area will be included in the ack-message, and
shown on the status page.


If that is not good enough, then we'll have to discuss how to do it 
for the next release.


Regards,
Henrik