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 Brent.McCrackin at Bell.ca PH: 416-353-0692 "Serenity through viciousness."
-----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: February 14, 2005 1:44 AM To: hobbit at hswn.dk 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
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On Mon, Feb 14, 2005 at 09:39:52AM -0500, brent.mccrackin at bell.ca 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
participants (2)
-
brent.mccrackin＠bell.ca
-
henrik＠hswn.dk