[hobbit] Alert Acknowledgment Codes
Charles Jones
jonescr at cisco.com
Tue Jan 25 10:12:14 CET 2005
Henrik Storner wrote:
>In <1106611848.27890.333.camel at localhost.localdomain> Daniel J McDonald <dan.mcdonald at austinenergy.com> writes:
>
>
>
>>On Mon, 2005-01-24 at 17:07 -0700, Charles Jones wrote:
>>
>>
>>>Would it be possible, when the status of something goes Red, to have the
>>>code printed somewhere on the status page, so that one could use the
>>>"Acknowledge alert" option and copy/paste it in, rather than having to
>>>get the incident code from email/pager? If we wanted to be really
>>>spiffy the acknowledge alert could even have a dropdown/list of current
>>>alerts so you wouldn't even have to type it :)
>>>
>>>
>
>
>
>>Then you wouldn't know that the person who was supposed to be notified
>>really was... Making them copy it off a pager is a cheap "2-factor"
>>authentication....
>>
>>
>
>Exactly. But I understand Charles' question, because I've been wanting
>to do something like that.
>
>Our monitoring is handled by a NOC manned 24x7, and when an alert
>pops up on the Hobbit NK view they raise a trouble-ticket in some
>other system. The NOC people dont get an e-mail or pager alert, but it
>would still be nice if they could acknowledge "yes, a TT has been
>raised about this" to get the problem off their monitor. So I will
>probably implement some way of putting an "acknowledge" function on
>the webpages - this would have to be protected with some sort of
>access control, obviously.
>
>
>
Currently I am simply using a .htaccess file to restrict access, which
has been working for me so far, but built-in access control would be
nice, particularly for Acks and for Maint.pl. If there were a proper
permissions system, you could even define what users could see which
groups of hosts! Ahhh I feel the feature creature sneaking up on us! :-)
-Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20050125/8596b647/attachment.html>
More information about the Xymon
mailing list