On 17.04.2014 12:44, David Young wrote:
Hi all,
I'm running into a problem whereby users can accidentally acknowledge
a critical alarm for an unlimited period of time, which is a potential
risk to our platform. I'd like to restrict how long an service can be
acknowledged for, based on hostgroup / hostname.
I've mocked up a similar system using an eventhandler on particular
services, which simply deletes any acknowledgements for the service if
it changes state, using the status.cmd file. However, I'm not sure
whether there's a more elegant way to tackle this.
Not sure if that's just a gui problem calculating a value based on some
thresholds (for example custom variables being set on the host) and
ignoring the value a user adds.
If you're requiring acknowledgements to be deleted on *every* state
change, you should set the sticky option to '0' instead of '2'.
Otherwise they will only get cleared once a service recovers from a
not-ok state.
Never seen such a use case before tbh, so no good ideas from my side here.
kind regards,
Michael
--
DI (FH) Michael Friedrich
michael.friedr...@gmail.com || icinga open source monitoring
https://twitter.com/dnsmichi || lead core developer
dnsmi...@jabber.ccc.de || https://www.icinga.org/team
irc.freenode.net/icinga || dnsmichi
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
