Thank you Filipp!    I believe your assessment is correct; eventually, I noticed (later that night) that the transform was working correctly.  Since I was forcing the recalculation, getting the error, and noting that the value wasn't changing, I thought it was broken entirely.   I've cleared the historic data, and now the data/graph is displaying correctly.   Appreciate the help and fast response as always!

Hi Filipp, you are my hero!!!  ;D Thanks for the infos. I truncate the table and postgres frees up the storage space... Many thanks! Greetings Marco

You can just do "Execute script" on your node and try the following script from there: r = $node.executeSSHCommand("ping 8.8.8.8 repeat 3 timeout 1"); println(typeof(r)); println(r); It will print the result of executeSSHCommand() function. One probable issue is that ssh communication goes through the agent that runs along with the server. So this agent should have SubAgent = ssh in it's configuration file (make sure you restart the agent after making the changes). To debug you can add DebugLevel = 6 to agent configuration file - agent log should give some information the moment when you execute your script.

Hi,  Quite a few things changes between these two version, one of them is that for performace reasons interfaces are synchronized only when needed. In most places this works quite transparently and they are received from the server as needed, but in object tree the search is actually a filter and finds only objects that are syncronized.  There's a setting that changes this behavior, it's in client's properties, Objects->Full object synchronization on startup

Try "regex" instead of "useRegex" like: {{host}}/objects?parent=4&class=interface&regex=true&name=%2F.%2AWI.%2A%2F

Hi,  A few changes were made in the code, including better logging and special handling if 0.0.0.0/0 subnet was received during network discovery. This will be included in next patch release that should be in the coming days.

In next patch release

PING3 is something niche and yes, looks that it's being auto-detected incorrectly. You can put PING3 into NetworkDeviceDrivers.BlackList server configuration parameter, this will prevent the auto-detection

Agent uses GetSecurityInfo win api function, please check information about needed access rights here: https://learn.microsoft.com/en-us/windows/win32/api/aclapi/nf-aclapi-getsecurityinfo#remarks

If I understand your correctly, this should be enough: InetAddress("10.5.3.0", 24).contains($node.ipAddress) This autobind script will collect all 10.5.3.0/24 nodes into container. $node.ipAddress is detected management address, if you want to do it based on the interfaces: for (i : $node.interfaces) { for (addr : i.ipAddressList) { if (InetAddress("10.5.3.0", 24).contains(addr)) { return true; } } } return false;

Yes, I think you are right - if it's SYS_NODE_UNREACHABLE, then alarm is not created and timers are not set.  Actually SYS_NODE_UP event has parameter at index 1 which is set to 1 if node is returning from "unreachable" state and 0 if from "down", so you can filter by that in your recovery EPP rule by the following script: return $event.getParameter("reason") != 1;

Just fixed it, fix ill be in next patch release. Thanks for reporting! Best regards, Victor

You can try to set debug level to 7, run instance discovery poll on node, and check server log file for lines with text queryWebService - it may give some hint at what is going on with request.

Thanks for the input - I will check on it asap and feedback here.

Tokens generated from Management Console are intended for different things - currently I think only for publishing network maps. So yes, current way it to get temporarily session id. UPD: actually permanent tokens are supported in the new API - the one that is server module and is currently under development. But not in the old one.

File uploads are kept under Configuration -> Scheduled tasks. In the menu (three-dot button on the toolbar) you need to enable "Show system tasks".

Hi, Sorry, you post got a bit lost. Current version is 5.2.3, I don't think there were any changes related to this, but anyways, pls upgrade to is to that we are on the same page. Then, when you observer such situation, pls check Event log for a node that had SYS_NODE_UNREACHABLE event. Check Root ID column for this ID, is it 0 or not? If not, pls find event with that ID. Pls show screenshots

Have not heard about some existing integration, so you'd need to develop something yourself. Main thing is what exactly you want to synchronize. From NetXMS side you can talk to NetBox's REST API using NXSL and web services. Also NetBox supports Webhooks, so may be it can talk to NetXMS REST API

For TSDB data is stored in the following tables - number in the name is the retention period IDATA_SC_7 IDATA_SC_30 IDATA_SC_90 IDATA_SC_180 IDATA_SC_OTHER IDATA_SC_DEFAULT If you DCI retention time is "Default", then IDATA_SC_DEFAULT table will be used. IDATA_SC_OTHER stores DCIs with duration longer the 180 days. You can check size of these tables (and also TDATA_SC_* for table DCIs) in your database

Objects.Nodes.ResolveNames - this works only when node is created.  There's Objects.Nodes.SyncNamesWithDNS, but this one is taking names from DNS only (also not that activating this parameter currently requires server restart which contradicts with what UI is saying - it's a bug)