<![CDATA[Maintenance in "Processing Policy"]]>Hello and thank you for this awesome monitoring tool.

I have a question regarding the new maintenance mode.

Is there any posibility to add a script in the "event processing policy", that is doing the following?

  • If node is in maintenance, then "return true", so that the action to be taken is "stop event processing"
  • else return false, to proceed to the next policies, till rule match.

Greetings from Germany,
Andreas

]]>https://forum.netxms.org/topic/4243/maintenance-in-processing-policyRSS for NodeFri, 13 Nov 2026 07:23:39 GMTFri, 22 Jan 2016 09:04:32 GMT60<![CDATA[Reply to Maintenance in "Processing Policy" on Fri, 22 Jan 2016 12:45:14 GMT]]>Aaaaah, ok. Thank you very much tomaskir.

Have to admit, I really start loving NetXMS. 😄

]]>https://forum.netxms.org/post/18935https://forum.netxms.org/post/18935Fri, 22 Jan 2016 12:45:14 GMT<![CDATA[Reply to Maintenance in "Processing Policy" on Fri, 22 Jan 2016 12:31:17 GMT]]>Just a bit more info on this:

When a node is put into the maintenance mode, all new events generated for that node are correlated to the "Node entered maintenance mode" event.
So any new events (after node is put into maintenance) do not actually enter EPP at all (since correlated events do not enter EPP).

When you double click on the "Node entered maintenance mode" alarm in the Alarm Browser, you can see all events that were correlated to the maintenance event.

]]>https://forum.netxms.org/post/18934https://forum.netxms.org/post/18934Fri, 22 Jan 2016 12:31:17 GMT<![CDATA[Reply to Maintenance in "Processing Policy" on Fri, 22 Jan 2016 12:20:12 GMT]]>OK, sorry it was my mistake. It seems there is no need to write a policy script for it.

I think I only had alarms from maintenance nodes (which I shut down), because of a polling delay. 🙂

Thread can be considered as closed.

]]>https://forum.netxms.org/post/18933https://forum.netxms.org/post/18933Fri, 22 Jan 2016 12:20:12 GMT