Hi, there is no default value for sticky acknowledgements in Icinga 1.x - you’ll pass the sticky attribute using the external command which requires the value being set - either to 0 (not sticky) or 2 (sticky).
http://docs.icinga.org/latest/en/extcommands2.html [—snip—] ACKNOWLEDGE_SVC_PROBLEM ACKNOWLEDGE_SVC_PROBLEM;<host_name>;<service_description>;<sticky>;<notify>;<persistent>;<author>;<comment> Allows you to acknowledge the current problem for the specified service. By acknowledging the current problem, future notifications (for the same servicestate) are disabled. If the "sticky" option is set to two (2), the acknowledgement will remain until the service recovers (returns to an OK state). Otherwise the acknowledgement will automatically be removed when the service changes state. If the "notify" option is set to one (1), a notification will be sent out to contacts indicating that the current service problem has been acknowledged, if set to null (0) there will be no notification. If the "persistent" option is set to one (1), the comment associated with the acknowledgement will remain even after the service recovers. [—snip—] Kind regards, Michael > On 24 Dec 2015, at 21:15, Felix Cruz <felix1...@gmail.com> wrote: > > Hi All > > Thanks for the info. We found that by default the acknowledgement is sticky. > Not a best practice OTS as the documentation leads one to believe that the > default behavior is NOT sticky. > > Learning the hard way is an understatement as I work for a Cloud provider and > this could have been a disaster of disastrous proportions. Did I say > disaster??? We've set the default to not sticky and I removed all my acks. > Almost missed the ones that already moved into critical. We act on critical > on these so it was an attempt to clear unhandled warnings of these, as it is > essentially noise based on when we act. > > I really think the default should be as the documentation says, which is that > it is removed on status change. > > Thanks again. > > > > Sent from my iPhone > > On Dec 24, 2015, at 12:46 PM, Markus Joosten <markus.joos...@plumbe.de> wrote: > >> Actually, this behaviour can be changed with the sticky bit of the >> acknowledgement, which is enabled by default if I remember correctly. >> >> When the sticky bit is removed, you should receive alerts for state changes >> from warning to critical, even when you already acknowledged the warning. >> >> Sent from my iPhone >> >> On 24 Dec 2015, at 16:18, Assaf Flatto <ici...@flatto.net> wrote: >> >>> Flix >>> >>> Acknowledging an alert tell the system that you are working on resolving >>> and it till clear one the state has moved to the "OK" state.I have >>> encountered it in similar situation and learned it the hard way, but >>> that is the outcome. >>> >>> So if you don't want to be alerted with a warning on such a low >>> threshold - change it to be more appropriate and not as easily dismissed. >>> >>> Assaf >>> >>> On 23/12/15 06:10, Felix Cruz wrote: >>> > Hi >>> > >>> > I have a basic question regarding expected behavior. Using Icinga >>> > version 1.13. I am with my company's monitoring team so not the >>> > administrator (with whom I will be discussing this as well ). >>> > >>> > We check for available space on Linux partitions. I acknowledged the >>> > service check while in Warning status with the belief that if it moved >>> > from Warning to Critical (W=25%, C=12%), the acknowledgement would be >>> > removed and it would be in Critical unhandled. It in fact stayed in >>> > Acknowledged status even when it moved into Critical. >>> > >>> > Is this the expected behavior? Documentation leads me to believe >>> > otherwise (7.2 List of External Commands). >>> > >>> > Thanks for any help. >>> > >>> > Sent from my iPhone >>> > _______________________________________________ >>> > icinga-users mailing list >>> > icinga-users@lists.icinga.org >>> > https://lists.icinga.org/mailman/listinfo/icinga-users >>> >>> _______________________________________________ >>> icinga-users mailing list >>> icinga-users@lists.icinga.org >>> https://lists.icinga.org/mailman/listinfo/icinga-users >>> >>> >>> >> _______________________________________________ >> icinga-users mailing list >> icinga-users@lists.icinga.org >> https://lists.icinga.org/mailman/listinfo/icinga-users > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users -- Michael Friedrich, DI (FH) Senior Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 CEO: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | michael.friedr...@netways.de ** OSDC 2016 - April - netways.de/osdc ** ** OSBConf 2016 - September - osbconf.org ** _______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
