Whilst we're on the subject of new features would it be possible to have easier access to the acknowledgement code for an alert? As things stand at the moment the only place that you can get the ack code is on the email notification that gets sent out once the alert has been triggered. With our setup this means that we have to wait for the frontline support people to contact us before we can ack the alert, even if we knew about it as soon as it happened.
What I'd like to be able to do is to pre-empt the alert by having access to the ack code earlier, as soon as the status changes to red, and have the code displayed on the individual test page. The way I envisage this happening is that the ack code is generated when the test turns red rather than when an alert is sent out. This code can then be included on the tests status page where we have easy access to it. The text could be displayed in a similar fashion to the text currently added when an alert is acknowledged.
I know that we could turn the test offline without the ack code but that tends to leave a hole in the graphs, acknowledging the alert allows everything to be logged/graphed as per normal.
Does this sort of behaviour sound feasible?
Thanks, Ian Marsh
On Tue, Apr 19, 2005 at 10:44:36AM, Marsh, Ian wrote:
Whilst we're on the subject of new features would it be possible to have easier access to the acknowledgement code for an alert? As things
I like that idea too
stand at the moment the only place that you can get the ack code is on
Actually in a situation like that I query against hobbitdboard to get the ACKCODE
bb 127.0.0.1 "hobbitdboard" | grep HOSTNAME | grep SERVICE
man bb for more details
the email notification that gets sent out once the alert has been triggered. With our setup this means that we have to wait for the frontline support people to contact us before we can ack the alert, even if we knew about it as soon as it happened.
-- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu "..there are two kinds of people: those who work and those who take the credit...try to be in the first group;...less competition there." - Indira Gandhi
On Tue, Apr 19, 2005 at 08:00:57AM -0400, Asif Iqbal wrote:
Actually in a situation like that I query against hobbitdboard to get the ACKCODE
bb 127.0.0.1 "hobbitdboard" | grep HOSTNAME | grep SERVICE
A simpler method (at least for the server to handle) is bb 127.0.0.1 "hobbitdboard host=HOSTNAME test=TESTNAME fields=cookie"
Henrik
On Tue, Apr 19, 2005 at 10:44:36AM +0100, Marsh, Ian wrote:
What I'd like to be able to do is to pre-empt the alert by having access to the ack code earlier, as soon as the status changes to red, and have the code displayed on the individual test page. The way I envisage this happening is that the ack code is generated when the test turns red rather than when an alert is sent out. This code can then be included on the tests status page where we have easy access to it. The text could be displayed in a similar fashion to the text currently added when an alert is acknowledged.
Try the attached patch - should work against 4.0.2. Apply with
cd hobbit-4.0.2 patch -p0 </tmp/hobbit-4.0.2-cookies.patch make stop hobbit make install (as root) start hobbit
This makes the cookie appear on the detailed status page if it has not yet been acknowledged. By default I've disabled this - you must add the option "--publish-cookies" to the hobbitsvc.cgi command in ~/server/cgi-bin/bb-hostsvc.sh to enable this.
I haven't yet made up my mind if this is a good idea or not. Another solution I've thought about is to make an acknowledge webpage similar to the enable/disable webpage, where you can choose which tests to acknowledge. And publishing the cookies on the status-page becomes more difficult with the planned changes to the alerting where escalations are handled.
Regards, Henrik
participants (3)
-
henrik＠hswn.dk
-
ian.marsh＠hants.gov.uk
-
iqbala-hobbit＠qwestip.net