<![CDATA[Automatic Alarm Resolve]]>Hi,

I have one problem about automatic alarm resolve. I have one recording system/device which can sent alarm for every fault in system via trap.
After receive trap NetXMS is configure to create alarm with some serial number. Unfortunately, recording device can't sent trap when system itself clear all active alarms.
Only way what I can do is auto resolving alarm when I got result 0 from reading DCI parameter "Active alarm" from this node using regular expression for all alarm of this node.
There is one problem. NetXMS always resolve all alarms for this node no matter that some of those alarms already resolved before. In this case I have only one date for "Last changes" in alarm table for all alarms of this node.
I don't now how filter only outstanding alarms in alarm function "Resolve all alarm with key" and regular expression. Maybe there some variable for the state of alarm (0,1,2,3 - Outstanding, acknowledged, resolved, terminated) which I can put in expressions filters.
If anyone have some good idea please help me to resolve this situation.

thanks in advance
Tomislav

]]>https://forum.netxms.org/topic/5832/automatic-alarm-resolveRSS for NodeFri, 13 Nov 2026 10:36:39 GMTFri, 08 Feb 2019 09:08:24 GMT60<![CDATA[Reply to Automatic Alarm Resolve on Thu, 14 Feb 2019 21:03:42 GMT]]>Thanks a lot,
Tomislav

]]>https://forum.netxms.org/post/25352https://forum.netxms.org/post/25352Thu, 14 Feb 2019 21:03:42 GMT<![CDATA[Reply to Automatic Alarm Resolve on Thu, 14 Feb 2019 20:24:50 GMT]]>Fix is already made, I plan to made release 2.2.13 within a week.

Best regards,
Victor

]]>https://forum.netxms.org/post/25350https://forum.netxms.org/post/25350Thu, 14 Feb 2019 20:24:50 GMT<![CDATA[Reply to Automatic Alarm Resolve on Thu, 14 Feb 2019 13:15:10 GMT]]>Thanks you Victor.
When you expect new revision where this bug will probably resolve?
Tomislav

]]>https://forum.netxms.org/post/25348https://forum.netxms.org/post/25348Thu, 14 Feb 2019 13:15:10 GMT<![CDATA[Reply to Automatic Alarm Resolve on Sat, 09 Feb 2019 09:17:31 GMT]]>Hi,

that's actually looks like a bug. If alarm is already resolved system should not change it's state. We will fix it for next release.

Best regards,
Victor

]]>https://forum.netxms.org/post/25335https://forum.netxms.org/post/25335Sat, 09 Feb 2019 09:17:31 GMT