<![CDATA[How to avoid the alarm flood of offline equipment chain?]]>I would like to ask the expert a question: if an aggregation device is disconnected, all the devices under it will be offline, and each device will send an alarm message at this time. How can we make sure that only the top device performs the action of sending alarm message, and the lower part relies on the device not to send alarm message?

]]>https://forum.netxms.org/topic/7625/how-to-avoid-the-alarm-flood-of-offline-equipment-chainRSS for NodeFri, 13 Nov 2026 09:44:42 GMTFri, 10 Feb 2023 13:57:40 GMT60<![CDATA[Reply to How to avoid the alarm flood of offline equipment chain? on Mon, 13 Feb 2023 15:07:58 GMT]]>Thank you very much for the pointers!

]]>https://forum.netxms.org/post/32258https://forum.netxms.org/post/32258Mon, 13 Feb 2023 15:07:58 GMT<![CDATA[Reply to How to avoid the alarm flood of offline equipment chain? on Mon, 13 Feb 2023 12:00:24 GMT]]>you can use a filtering script in the EPP and match for the names of the nodes you want to dismiss. something like this:

if($node->name match "^unwanted_node.+")
{
    return false;
}
return true;
]]>https://forum.netxms.org/post/32255https://forum.netxms.org/post/32255Mon, 13 Feb 2023 12:00:24 GMT<![CDATA[Reply to How to avoid the alarm flood of offline equipment chain? on Mon, 13 Feb 2023 10:26:41 GMT]]>Thank you very much, but  if  manually exclude the child nodes, it is too much trouble,  can there be any rule than can  automatically adapte  to it?

]]>https://forum.netxms.org/post/32251https://forum.netxms.org/post/32251Mon, 13 Feb 2023 10:26:41 GMT<![CDATA[Reply to How to avoid the alarm flood of offline equipment chain? on Mon, 13 Feb 2023 08:28:09 GMT]]>A quick solution would be to exclude the child nodes from source objects in the EPP for that rule.

]]>https://forum.netxms.org/post/32249https://forum.netxms.org/post/32249Mon, 13 Feb 2023 08:28:09 GMT