[hobbit] Some thoughts about alerts, acks and escalations

[Daniel Deighton]

This would be extremely useful.  I agree with Richard.  Full control of
the escalation times would be very beneficial.

On Wed, 2005-04-13 at 08:24 -0400, Deal, Richard wrote:
> Yes this sound useful, especially if there is any easy way to set when
> the alerts start going to the next level up.  An escalation delay, for
> example that would determine how long something is in alert before going
> to the next level.  Would be nice to be able to set the escalation delay
> globally, and to change it per host.  Might also be nice (for some) to
> have different delays for each escalation level (10 mins from 0-to-1,
> but 30 mins from 1-to-2)?
> 
> -----Original Message-----
> From: Henrik Stoerner [mailto:henrik at hswn.dk] 
> Sent: Wednesday, April 13, 2005 1:49 AM
> To: hobbit at hswn.dk
> Subject: [hobbit] Some thoughts about alerts, acks and escalations
> 
> I'm beginning to look at the issue of escalating alerts. And I've had
> an idea that I'd like to get some feedback on before I go ahead and
> implement it.
> 
> Right now, Hobbit doesn't handle escalating an alert. When someone
> receives an alert message, they can ack it - when they do, all alerts
> stop and the item disappears from the "Critical systems" page (the NK
> page).
> 
> BB has the concept of escalating an alert, meaning that some
> recipients of an alert will get the alert message even if the alert
> has been acknowledged.
> 
> 
> What I'd like to have is the BB system with a finer granularity. A
> recipient in the hobbit-alerts.cfg file has an associated "level",
> default is 1.
> 
> I want our NOC guys who do nothing but stare at the NK page 24x7 to be
> able to acknowledge an alert - and that just gets it off their
> monitor, it doesn't stop alerts from going out. A "level 0"
> acknowledgment - this is just to log that a trouble ticket has been
> raised for the issue.
> 
> A technician (who is a "level 1" recipient) can acknowledge the alert
> he receives - this will stop alert messages from going out to other
> "level 1" receipients, so all of the engineers can concentrate on
> doing what needs to be done. 
> 
> Alerts will still be sent to recipients who are "level 2" and above -
> these are the equivalent of the BB "escalation" alerts. They can ack
> the alert if they'd like to turn off more alert messages, of course.
> 
> You can have even higher levels if you like, probably going up the
> hierarchy of managers. I don't think we'll using more than the 3
> levels I've described, but there is no reason to impose any limit.
> 
> 
> Does that sound like it would be useful?
> 
> 
> Regards,
> Henrik
> 
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe at hswn.dk
> 
> 
> 
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe at hswn.dk
> 
> 
-- 
Daniel Deighton <dan at deightime.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20050413/a625f080/attachment.sig>