<![CDATA[Alert Notifier does not match alarm viewer or in Console]]>I have noticed that the alarm notifer has identified a number of alarms that do not appear in either the alarms viewer or console.  Specifially it shows that a number of nodes have dropped out late at night, but I assume that they have came back on-line not much later.

Are these not appearing in the console because the nodes have come back online?  If this is the case, is there a way to maintain these alarms so that I know that they have occured - such as a history of all alarms created against a node?

It's a smart piece of software BTW...

]]>https://forum.netxms.org/topic/792/alert-notifier-does-not-match-alarm-viewer-or-in-consoleRSS for NodeFri, 13 Nov 2026 11:31:06 GMTSun, 13 Dec 2009 21:59:55 GMT60<![CDATA[Reply to Alert Notifier does not match alarm viewer or in Console on Thu, 17 Dec 2009 16:19:43 GMT]]>It's actually a bug in alarm notifier - it does not update alarm list correctly.

For knowing that node was offline for some time and then go back online, you can do the following:
Instead of terminating node down alarm when SYS_NODE_UP event received, generate new alarm with NORMAL priority which will replace "Node down" alarm. Than you will know that node was down for some time. Then you have 3 options to terminate those "Node up" alarms:

  1. Terminate them manually;
  2. Create a script that will use nxalarm command line utility to periodically read active alarms and terminate "Node up" alarms which are older than some time period;
  3. Set alarm timeout for "Node up" alarms and terminate them when alarm timeout event comes.

Best regards,
Victor

]]>https://forum.netxms.org/post/3723https://forum.netxms.org/post/3723Thu, 17 Dec 2009 16:19:43 GMT