<![CDATA[Difference between Acknowledge and Sticky Acknowledge]]>Hello,

Please, can someone explain difference between "Acknowledged" and "Sticky Acknowledged" alarm states? What is "Sticky Acknowledge" action good for?

Thanks & Regards,
Lukas

]]>https://forum.netxms.org/topic/2088/difference-between-acknowledge-and-sticky-acknowledgeRSS for NodeFri, 13 Nov 2026 10:34:44 GMTWed, 19 Dec 2012 06:53:28 GMT60<![CDATA[Reply to Difference between Acknowledge and Sticky Acknowledge on Wed, 19 Dec 2012 12:04:20 GMT]]>Thank you for the reply, this looks as a very useful feature.

]]>https://forum.netxms.org/post/9193https://forum.netxms.org/post/9193Wed, 19 Dec 2012 12:04:20 GMT<![CDATA[Reply to Difference between Acknowledge and Sticky Acknowledge on Wed, 19 Dec 2012 10:58:36 GMT]]>Normally, when alarm's repeat count increases (because new event was matched to existing alarm by alarm's key), alarm's state reset to "outstanding". To prevent this, you can use "sticky acknowledge". In that state, alarm will remain acknowledged event after new matching events.
This can be useful when you know that there will be new matching events, but it will not change the situation. For example, if you have network device which will send new SNMP trap every minute until problem solved, sticky acknowledge will help to eliminate unnecessary outstanding alarms.

Best regards,
Victor

]]>https://forum.netxms.org/post/9186https://forum.netxms.org/post/9186Wed, 19 Dec 2012 10:58:36 GMT<![CDATA[Reply to Difference between Acknowledge and Sticky Acknowledge on Wed, 19 Dec 2012 07:41:33 GMT]]>I believe, "Sticky Acknowledged" won't be reset if the alarm reappears.

]]>https://forum.netxms.org/post/9184https://forum.netxms.org/post/9184Wed, 19 Dec 2012 07:41:33 GMT