<?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[Templates & Instance Discovery]]></title><description><![CDATA[<p dir="auto">Is it possible to use Instance Discovery within a DCI configured to a Template?  I've tried to configure this according to youTube videos and instructions on the Wiki, but it seems the DCIs never get created on the actual node after applying Template when using Instance Discovery.</p>
<p dir="auto">I'm running 1.2.12 on Windows 2008 with SQL 2008.  Any help would be appreciated.</p>
]]></description><link>https://forum.netxms.org/topic/2998/templates-instance-discovery</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 12:05:40 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/2998.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 16 Mar 2014 02:53:45 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Templates & Instance Discovery on Tue, 27 Oct 2015 15:41:28 GMT]]></title><description><![CDATA[<p dir="auto">Just an update - since this topic is the top google result for NetXMS Agent Instance discovery.</p>
<p dir="auto">With 2.0 there is a new agent list "Net.InterfaceNames" which contains all interface names present on a node.<br />
You can use this list as instance discovery source, without a need for any filtering script.</p>
<p dir="auto">Screenshots attached.</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000002595-agent_instance_discovery_1.PNG" alt="agent_instance_discovery_1.PNG" class="img-markdown  img-fluid" width="672" height="634" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000002597-agent_instance_discovery_2.PNG" alt="agent_instance_discovery_2.PNG" class="img-markdown  img-fluid" width="672" height="636" /></p>
]]></description><link>https://forum.netxms.org/post/18123</link><guid isPermaLink="true">https://forum.netxms.org/post/18123</guid><dc:creator><![CDATA[tomaskir]]></dc:creator><pubDate>Tue, 27 Oct 2015 15:41:28 GMT</pubDate></item><item><title><![CDATA[Reply to Templates & Instance Discovery on Mon, 20 Oct 2014 13:44:03 GMT]]></title><description><![CDATA[<p dir="auto">That's very strange. I just test it just in case, and it works as expected. Let's try to delete all DCIs already created and create new one from scratch to be sure that everything is correct, and then run configuration poll so instance discovery will occur.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/15088</link><guid isPermaLink="true">https://forum.netxms.org/post/15088</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Mon, 20 Oct 2014 13:44:03 GMT</pubDate></item><item><title><![CDATA[Reply to Templates & Instance Discovery on Mon, 20 Oct 2014 12:33:23 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">here come the screenshots from my DCI.<br />
The OS is WIN 7 Prof. (64 Bit)</p>
<p dir="auto">Using "nxget -l &lt;host&gt; Net.InterfaceList" on the Server delivers 2 Interfaces with IP and other informations. So for me it seems correct.</p>
<p dir="auto">Sorry if this is a dumb question but we are currently checking if netxms could be an alternative for our already outdated NAGIOS Installation. Cause of this i'm trying a lot of things to check what's possible an what might not.</p>
<p dir="auto">Best regards<br />
Haari</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000002014-dci1.PNG" alt="dci1.PNG" class="img-markdown  img-fluid" width="656" height="657" /></p>
<p dir="auto"><img src="/assets/uploads/files/smf/0000000002016-dci2.PNG" alt="dci2.PNG" class="img-markdown  img-fluid" width="661" height="658" /></p>
]]></description><link>https://forum.netxms.org/post/15085</link><guid isPermaLink="true">https://forum.netxms.org/post/15085</guid><dc:creator><![CDATA[Haari]]></dc:creator><pubDate>Mon, 20 Oct 2014 12:33:23 GMT</pubDate></item><item><title><![CDATA[Reply to Templates & Instance Discovery on Mon, 20 Oct 2014 11:56:47 GMT]]></title><description><![CDATA[<p dir="auto">It could be that your agent does not support 64 bit interface counters (they are supported only on Windows Vista and later). Then you have to use Net.Interface.BytesIn.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/15084</link><guid isPermaLink="true">https://forum.netxms.org/post/15084</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Mon, 20 Oct 2014 11:56:47 GMT</pubDate></item><item><title><![CDATA[Reply to Templates & Instance Discovery on Mon, 20 Oct 2014 11:12:19 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/haari" aria-label="Profile: haari">@<bdi>haari</bdi></a> said in <a href="/post/15080">Templates &amp; Instance Discovery</a>:</p>
<blockquote>
<p dir="auto">Hello,</p>
<p dir="auto">tried to do the same Thing like zsing82 but i'm always getting an error:</p>
<p dir="auto"><em>Status of DCI 98 (NetXMS Agent: Net.Interface.BytesIn64()) changed to UNSUPPORTED</em></p>
<p dir="auto">It seems that there is something wrong with the "instance". the filtering script is exactly the one from victors post.</p>
<p dir="auto">I tried something similar with my hdd's and "FileSystem.MountPoints" as Instance List. This list works and delivers me all the wanted Information. But for the Network Interfaces i end up with this "unsupported"-error.</p>
<p dir="auto">Any ideas?</p>
<p dir="auto">Kind Regards<br />
Haari</p>
</blockquote>
<p dir="auto">Attach a screenshot of how your DCI is configured please.</p>
]]></description><link>https://forum.netxms.org/post/15082</link><guid isPermaLink="true">https://forum.netxms.org/post/15082</guid><dc:creator><![CDATA[tomaskir]]></dc:creator><pubDate>Mon, 20 Oct 2014 11:12:19 GMT</pubDate></item><item><title><![CDATA[Reply to Templates & Instance Discovery on Mon, 20 Oct 2014 11:07:34 GMT]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">tried to do the same Thing like zsing82 but i'm always getting an error:</p>
<p dir="auto"><em>Status of DCI 98 (NetXMS Agent: Net.Interface.BytesIn64()) changed to UNSUPPORTED</em></p>
<p dir="auto">It seems that there is something wrong with the "instance". the filtering script is exactly the one from victors post.</p>
<p dir="auto">I tried something similar with my hdd's and "FileSystem.MountPoints" as Instance List. This list works and delivers me all the wanted Information. But for the Network Interfaces i end up with this "unsupported"-error.</p>
<p dir="auto">Any ideas?</p>
<p dir="auto">Kind Regards<br />
Haari</p>
]]></description><link>https://forum.netxms.org/post/15080</link><guid isPermaLink="true">https://forum.netxms.org/post/15080</guid><dc:creator><![CDATA[Haari]]></dc:creator><pubDate>Mon, 20 Oct 2014 11:07:34 GMT</pubDate></item><item><title><![CDATA[Reply to Templates & Instance Discovery on Tue, 18 Mar 2014 15:58:23 GMT]]></title><description><![CDATA[<p dir="auto">Thank you very much for your help!  That worked perfectly.  I never would've figured out that script</p>
]]></description><link>https://forum.netxms.org/post/13183</link><guid isPermaLink="true">https://forum.netxms.org/post/13183</guid><dc:creator><![CDATA[zsing82]]></dc:creator><pubDate>Tue, 18 Mar 2014 15:58:23 GMT</pubDate></item><item><title><![CDATA[Reply to Templates & Instance Discovery on Tue, 18 Mar 2014 15:47:28 GMT]]></title><description><![CDATA[<p dir="auto">Hi!</p>
<p dir="auto">You can transform instance values in instance filtering script. Fltering script can return an array consisting of two elements - true/false flag and new instance value. For extracting interface index from interface list you can use the following script:</p>
<pre><code>if ($1 ~= "^([0-9]+) .*")
{
   return %(true, $1);  // at this point $1 contains first matching group
}
return false;
</code></pre>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/13181</link><guid isPermaLink="true">https://forum.netxms.org/post/13181</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Tue, 18 Mar 2014 15:47:28 GMT</pubDate></item><item><title><![CDATA[Reply to Templates & Instance Discovery on Tue, 18 Mar 2014 15:16:39 GMT]]></title><description><![CDATA[<p dir="auto">OK, one of the things I'm trying to do is collect bandwidth consumption from Windows hosts and servers running NetXMS Agent.</p>
<p dir="auto">Here's what I have:<br />
A template named "Agents" with Automatic Apply script as</p>
<pre><code>return $node-&gt;isAgent;
</code></pre>
<p dir="auto">Template "Agents" contain multiple DCIs.  I have 2 specific DCIs:</p>
<pre><code>Number of input bytes on interface {instance}
Number of output bytes on interface {instance}
</code></pre>
<p dir="auto">with source being "NetXMS Agent"; data type "UnsignedInt64"; and parameters as follows:</p>
<pre><code>Net.Interface.BytesIn64({instance})
Net.Interface.BytesOut64({instance})
</code></pre>
<p dir="auto">The "Instance Discovery" page is where I think I'm getting something wrong.  For both DCIs, I have "Agent List" as discovery method and List Name is "Net.InterfaceList".  This list returns the <em>ifIndex</em>, <em>IP Address</em>, <em>ifType</em>, <em>MAC Address</em>, and <em>ifDesc</em>.<br />
I'd like to transform the list results so that only <em>ifIndex</em> is returned to {instance}, but I have no idea how to do that.  Is this even possible using Templates?</p>
<p dir="auto">P.S.  I'd also like to perform similar action with FileSystem.FreeSpace%, etc...</p>
]]></description><link>https://forum.netxms.org/post/13162</link><guid isPermaLink="true">https://forum.netxms.org/post/13162</guid><dc:creator><![CDATA[zsing82]]></dc:creator><pubDate>Tue, 18 Mar 2014 15:16:39 GMT</pubDate></item></channel></rss>