<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Apply status to interface from DCI threshold on switch]]></title><description><![CDATA[<p dir="auto">I've been playing with netxms this week for the first time and have been loving it!<br />
I have created a DCI for an interface to measure the current bits/s by right clicking it and using the built-in 'create data collection items'.<br />
I've also successfully created the thresholds and the events are firing in the event monitor when they're met.<br />
However, if I configure event processing to generate an alarm, the alarm is put on the switch and not the interface itself.<br />
Is there a way to make the alarm generate on the interface? I've looked through the admin guide and searched around, but maybe I'm missing something simple.</p>
<p dir="auto">Thanks!</p>
]]></description><link>https://forum.netxms.org/topic/7033/apply-status-to-interface-from-dci-threshold-on-switch</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 18:06:24 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/7033.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 28 Apr 2021 17:03:22 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Apply status to interface from DCI threshold on switch on Fri, 30 Apr 2021 14:51:17 GMT]]></title><description><![CDATA[<p dir="auto">Got it, thank you very much for explaining!</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000005483-2021-04-30_09_50_53-NetXMS_Management_Console_-_admin_10.0.0.220_.png" alt="2021-04-30 09_50_53-NetXMS Management Console - admin@10.0.0.220.png" class="img-markdown  img-fluid" width="678" height="296" /></p>
]]></description><link>https://forum.netxms.org/post/29935</link><guid isPermaLink="true">https://forum.netxms.org/post/29935</guid><dc:creator><![CDATA[metheos]]></dc:creator><pubDate>Fri, 30 Apr 2021 14:51:17 GMT</pubDate></item><item><title><![CDATA[Reply to Apply status to interface from DCI threshold on switch on Fri, 30 Apr 2021 05:55:54 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">changing color of the link is also possible if it has DCIs associated - then you can select option "include active thresholds into calculation" in link properties and it will change color if there is active threshold on one of associated DCIs. Side effect is that values of those DCIs will be displayed on the link as well.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/29933</link><guid isPermaLink="true">https://forum.netxms.org/post/29933</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Fri, 30 Apr 2021 05:55:54 GMT</pubDate></item><item><title><![CDATA[Reply to Apply status to interface from DCI threshold on switch on Fri, 30 Apr 2021 02:38:53 GMT]]></title><description><![CDATA[<p dir="auto">Ok, that makes sense. I'm probably going about this the wrong way then?<br />
I've seen screenshots where people have a connector between 2 devices on a map where the connector color changes based on bandwidth usage.<br />
I assumed I had to apply the status to the interface and set the color of the connector to the status of the interface.<br />
What's the proper way to do this where a DCI threshold changes the color of a connector and doesn't affect the status of one of the switches it connects?</p>
]]></description><link>https://forum.netxms.org/post/29932</link><guid isPermaLink="true">https://forum.netxms.org/post/29932</guid><dc:creator><![CDATA[metheos]]></dc:creator><pubDate>Fri, 30 Apr 2021 02:38:53 GMT</pubDate></item><item><title><![CDATA[Reply to Apply status to interface from DCI threshold on switch on Thu, 29 Apr 2021 05:48:03 GMT]]></title><description><![CDATA[<p dir="auto">That's how  the system is built - while interfaces exist as child objects of a node, events and alarms are created on the node itself.<br />
Interface name is present in event's parameters, so if you need it for some custom processing in Event Processing Policy, you can get it there using NXSL (the built-in scripting language).</p>
]]></description><link>https://forum.netxms.org/post/29925</link><guid isPermaLink="true">https://forum.netxms.org/post/29925</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Thu, 29 Apr 2021 05:48:03 GMT</pubDate></item></channel></rss>