On Wed, 21 May 2014, Michael Friedrich wrote:
On 17.04.2014 12:44, David Young wrote:
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.
Never seen such a use case before tbh, so no good ideas from my side here.
Take a look at the "set_expire_ack_by_default" and
"default_expiring_acknowledgement_duration" configuration variables
in cgi.cfg (and hopefully in the doco).
I made the case for those based on the deeply disfunctional
organisation I used to work for (and which I mercifully have escaped)
where stuff would get ack'ed with the best of intentions and then all
the priorities changed and then never got worked on (incompetent
management); then there were times where they'd get ack'ed just to
shut the problems up and mask them because the monitoring system was
used as a cudgel to beat up the techs (pernicious management).
Expiring ACKs by default made those scenarios less likely as
it requires a deliberate action on the part of the person acknowledging
a problem to make it non-expiring. It helped a lot in my sad case;
perhaps it'll help here, too.
Cheers!
+------------------------------------------------+---------------------+
| Carl Richard Friend (UNIX Sysadmin) | West Boylston |
| Minicomputer Collector / Enthusiast | Massachusetts, USA |
| mailto:crfri...@rcn.com +---------------------+
| http://users.rcn.com/crfriend/museum | ICBM: 42:22N 71:47W |
+------------------------------------------------+---------------------+
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
