<div class="gmail_quote">2009/1/21 Mathieu Gagné <span dir="ltr"><<a href="mailto:mgagne@iweb.com">mgagne@iweb.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
Here is the situation:<br>
Somebody acknowledges a problem and forget about it.<br>
<br>
How would you implement an acknowledgement escalation?<br>
<br>
Or how would you detect such situation where a host/service is<br>
down/critical for too long while being acknowledged?<br>
<br>
--<br>
Mathieu<br>
<br>
</blockquote><div><br>Mmmm, there are a couple of technology things you could do for this, but the root of this problem is people, not computers. You need to work our a process where people aren't ack'ing things just so they can fall back asleep. I personally suggest having nagios create a ticket with whatever ticketing system you use (you use one right?!) so you can track that issue. That and having a 24x7 NOC helps :)<br>
<br>Otherwise, write something that takes a look at the status file and find services that are in a non-okay state but acknowledged and have been for however long. I wrote a simple nagios CFG parser that would be able to handle it that's under the GPL at my former company for their Oracle Monitoring: <a href="https://code.bluegecko.net/wiki/Monocle">https://code.bluegecko.net/wiki/Monocle</a>. There is another one that will probably work somehwere on cpan.<br>
<br>I would probably write that program to un-acknowledge things as well as alarming. If it just alarmed, someone might acknowledge it and do nothing about it. (since that's the problem you're having) You can do the un-acknowldeging though the nagios cmd file:<br>
<br><a href="http://www.nagios.org/developerinfo/externalcommands/commandinfo.php?command_id=116">http://www.nagios.org/developerinfo/externalcommands/commandinfo.php?command_id=116</a><br><a href="http://www.nagios.org/developerinfo/externalcommands/commandinfo.php?command_id=117">http://www.nagios.org/developerinfo/externalcommands/commandinfo.php?command_id=117</a><br>
<br>You can get the location of the command file from the macro <a name="commandfile">$COMMANDFILE$.</a><br><br>Cheers,<br><br>.r'<br><br></div></div>