To filter CD/DVD and Volume in the "Instance Detection" section, I use this script: type=AgentReadParameter($node, "FileSystem.Type(" . $1 . ")"); if ((type == null) || (type == "") || (type == "CDFS") || (type == "UDF")) { return false; } if ( type != null && ( type == "aufs" || type == "autofs" || type == "cgroup" || type == "configfs" || type == "debugfs" || type == "devpts" || type == "devtmpfs" || type == "fusectl" || type == "fuse.gvfsd-fuse" || type == "fuse.lxcfs" || type == "hugetlbfs" || type == "iso9660" || type == "mqueue" || type == "nfsd" || type == "overlay" || type == "proc" || type == "pstore" || type == "rpc_pipefs" || type == "securityfs" || type == "selinuxfs" || type == "squashfs" || type == "sysfs" || type == "tmpfs" )) { return false; } if (($1 == "/proc") ||     ($1 like "/proc/*") ||     ($1 == "/sys") ||     ($1 like "/sys/*") ||     ($1 == "/run") ||     ($1 like "/run/*") ||     ($1 == "/dev") ||     ($1 like "*Volume*") ||     ($1 like "/dev/*"))   return false; return true;

Map improvements are currently in development, expected to be included to 5.0 in a few months.

Great, thanks for all your hard work. We are getting into the system and it's really great, lots of rooms for scripts and customization!

Thank you very much, I suspected that from some of the java logs. Removing Java 11 and installing Java  17 solved the issue.  Regards.

Thank you very much!

Yes, that's exactly how it works. If at some point server would be able to get info about interfaces from agent, this interface will be recreated with proper name.

Hello Filipp, You are correct, I have installed the latest version on another server and it is indeed not behaving the same. The filter remains as configured initially. Thank you!

Great, thanks for update

@alk said in 4.4.2 Crash: Do you have any non-Ethernet interfaces there with MAC address longer than 6 bytes? not that i can see

Hi, I have been using an older version of NetXMS on a Windows 2012 R2 server for some time and it had worked fine. As part or our server upgrade plans we setup a new server running Windows 2019 and installed NetXMS 4.4.2 with Microsoft SQL. Installation went through fine and we were able to discover switches and devices in our estate, however, once of the tools I found extremely useful (find switch port) is no longer working on the new installation. Every time I target a device and search under "Tools > IP Address Search" I get an error saying "Found node XXX but it's connection point is unknown". I have looked through NetXMS documentation and various forums but am yet to find a fix. Has anyone else come across this issue? I would greatly appreciate any information you could share in support of a fix. Thanks Sam

If this web site supports standard authentication methods, you can use Web Services. In this case you have to create web service definition (with "Process response as plain text") and then can have a DCI with Web Service source and metric web_service_name:some text that should be on the web page Then you can have theshold for data collection error. Or alternatively you can have script DCI that would call web service using NXSL function.

I think you can create “app password” in profile and use it for authentication.

Hi! The legacy nxmc that you are using is going to be phased out in a few months, so there's no much sense in fixing this issue. If you have any issues or usability problems using nxmc-4.4.2-standalone.jar, please report them here so that these can be addressed.

Hi! You can just grep agent sources for any built-in agent table name, e.g. Agent.SubAgents and you will find the code, e.g: https://github.com/netxms/netxms/blob/master/src/agent/core/subagent.cpp#L301 Also, it's possible to configure external tables, this way agent would call an external process that provides table data.

If you've tried the new UI some time ago - at some point the icons on the left were arranged in a bit more logical way. I was kinda struggling before, but now Infrastructure services is the top one icon and things are way better. Also to note - a few things - e.g. data collection is moved from the node context menu to a tab. In overall - it took some time for me to get used to the new UI, but now it feels more comfortable then the old one (also still has some minor things to improve)

Transformation script is launched when data collection returns some value. As far as I understand, it will not be launched if data collection returned error.

There is no such option in the driver. However, it is possible to use configuration poll hook to test if node name is "name" and driver is "TELTONIKA", and rename it as desired. Sample script that does this and sets node name to product name: if ($node->name == 'name' and $node->driver == 'TELTONIKA') { $node->rename($node->productName); } Best regards, Victor

Hi, try just 59 * * * 6-7 for second schedule - it should have same effect. Best regards, Victor

Hi, Filipp. Awesome ! Thanks.

I am not an expert in nginx, but here's a config that I know is working: server { listen 443 ssl http2; ssl_certificate /etc/ssl/certs/xxxxx.pem; ssl_certificate_key /etc/ssl/private/xxxxx.pem; server_name xxxxx nx.local; root /var/www/html; location = / { return 301 /nxmc-light.app; } location / { proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Frame-Options SAMEORIGIN; proxy_pass http://10.10.10.10:8080/; } }