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
