Many thanks, had to adjust script litle bit, but got it working. m = $1 match "(.+)\[.+\]"; if (m) { return %(true, $2, m[1]); } else { return false; }

Upgrades are incremental, so you can safely go directly to the latest version, "nxdbmgr upgrade" will handle all steps correctly. Should be safe, but I'd backup first anyway. EDIT: I tried upgrade from empty 1.2.17 database and found a small bug with the upgrade. Either wait for next release, or apply https://github.com/netxms/netxms/commit/b30dfa64644c639d177f4367bc6de13ff4708311 and rebuild. Another option will be upgrading to some intermediate version, but I'm not sure which will work correctly (2.x something should work, but it will be trial and error).

Hello. You need to upgrade Java to version 11 or newer.

After some trial and error got some json output from this command: curl -k -u admin http://netxms:8080/webapi/alarms -X GET -d '{"alarm":"outstanding"}' It is returning all alarms regardless of whether they are NORMAL, WARNING, CRITICAL but its a start.

Great, that works! Thanks! I still think a "setThresholds()" method would be nice, but I'm glad I can go on now.   

Since 3.7 minimal java version is 11

Just in case, it's possible to read port forwarding database from NXSL - it's available in Topology.SwitchForwardingDatabase internal table. There's no access to L3 routing information yet, but it's planned to add https://track.radensolutions.com/issue/NX-1999

Hi, log viewer has also limit on number of records retrieved in one request. You can press "get more data" icon in log viewer to get next batch. Unfortunately this limit is hard coded and cannot be changed. Best regards, Victor

It's not fully implemented. It adds System.Execute action (and also System.ExecuteInAllSessions on Windows), but System.Execute does nothing. Updated docs.

As per your example above, JSON parser is failing on this part: "antenna_gps": {"py/tuple": [01.12343455, 02.45542]} You can check the syntax e.g. with this tool https://jsonformatter.curiousconcept.com So I suppose that the data returned by this web service might change time after time and sometimes the data confirms with what the JSON parser expects.

Just as a Bit of Info for nayone working with SNMP Monitoring - May count as Different Topic - But this was where I found the Idea for my fix. Just had this issue - Had a Site move from Ubiquiti Airmax gear to Unifi - IP range remained, but Devices were changed.  Some of them picked up old IP's, but as they already had a device in XMS previously - that device was updated with the new info - so Templates etc remained. The problem for me is that while my template was searching for the OID - I had been returning null on it - therefor it was just skipping the check... basically (from what I understand).  Changing to False has fixed that. However the code later has another "if-else" with a false - so not quite sure whats going on here... It certainly picks up the Positive, but doesn't appear to drop the negative.  But haven't touched this in months - so not the biggest autority on all this. Heres some code for a look over (Regarding Ubiquiti Airmax 2ghz devices - this is the edited version with the airMaxFrequency - now returning false...)  Hope this helps a fellow forum trawler. oid_airMaxFrequency = ".1.3.6.1.4.1.41112.1.4.1.1.4.1"; oid_airMaxSSID = ".1.3.6.1.4.1.41112.1.4.5.1.2.1"; querySNMP = CreateSNMPTransport($node); if (querySNMP == null) return null; airMaxFrequency = SNMPGetValue(querySNMP, oid_airMaxFrequency); if (airMaxFrequency == null) return false; /* airMaxSSID = SNMPGetValue(querySNMP, oid_airMaxSSID); */ /* if (airMaxSSID ~= "HQBH") */ /* return false; */ if (airMaxFrequency == "2412" || airMaxFrequency == "2417" || airMaxFrequency == "2422" || airMaxFrequency == "2427" || airMaxFrequency == "2432" || airMaxFrequency == "2437" || airMaxFrequency == "2442" || airMaxFrequency == "2447" || airMaxFrequency == "2452" || airMaxFrequency == "2457" || airMaxFrequency == "2462" || airMaxFrequency == "2467" || airMaxFrequency == "2472") { return true; } else { return false; }

Have been trying to get back into building our monitoring NXMS... now have hit a bit of a road block. Am getting info into logs - but appears I can only filter by Time and Date, and some others I am not yet interested in - while a filter that requres the selection of an object fails to place the object as a filter. Am Primarily doing SNMP monitoring, and am at the stage where i am trying to sort out what gets logged and what doesn't, but not being able to see whats happening over time with a praticular device is a big issue. Have tried Logging into console as system, and Running as admin, but have not been able to use Source or Zone Filters.  Just checked and Event object selection actually works. Currently on Version 3.7.95 - if anyone has some info as to how to make these work - would be appreciated.

Thank you! 

Thank you for the detailed response. This is exactly what I needed.

The problem is fixed now by permitting server IP in ACL on the router for accepting the SNMP queries. Thank You Filipp.

Many thanks for greate examples, got it working and went with mapping table version. Egert

You can ping external IP address. For that set up the DCI on a node that has NetXMS agent (that could be the same node where you have netxms server - normally you should have netxms agent running there). Select DCI origin "Agent" and use ICMP.PacketLoss(8.8.8.8) parameter.

I cannot believe that people are happy with the extremely limited range of map icons/images  or do people not create maps ?

Cool this is working really well now - thankyou

It's strange - there are no errors on either side, server reports normal connection closure: 2020.12.16 16:35:57.592 *D* [client.session.0  ] readSocket: connection closed Timestamps are also quite old and not in sync between server and client - do you have correct time on server and client? If yes, are those logs latest for version 3.7? Also, are they in same time zone? Best regards, Victor