NetXMS Support Forum

Update: we published patch release 5.0.1 that contains fix for bug in database upgrade procedure. Make sure that you are installing version 5.0.1.

We just published NetXMS version 5.0. This major release was mostly focused on improving network maps, wireless network monitoring, internal scripting language (NXSL), and new UI. And of course there is lot of smaller improvements and fixes.

Make sure to check list of breaking changes, as there are few.

Full change log is following:
-  Improved network maps
-  Added network map link styling script
-  Delegate access option that allows read access to network maps without full read access to objects on a map
-  Reworked monitoring of wireless access points and controllers
-  Major overhaul of sensor objects
-  Many NXSL function deprecated in favor of object methods
-  Improved NXSL classes and functions for date/time handling
-  Add option to check alarm details from alarm log view
-  Log parser rules can define metrics that are populated from match data
-  Special NXSL return codes for data collection and transformation scripts (DataCollection::ERROR, DataCollection::NOT_SUPPORTED, DataCollection::NO_SUCH_INSTANCE)
-  New NXSL function FindAccessPointByMACAddress
-  New NXSL function GetMappingTableKeys
-  "Stop" function in script executor view
-  Desktop client can reconnect automatically after short connectivity loss
-  New agent metric File.Hash.SHA256
-  New agent list and table Net.IP.Neighbors
-  Index property displayed in MIB browser
-  Root object can be set for object query
-  Improved SNMP trap processing performance
-  New log parser file option "removeEscapeSequences"
-  Added peer certificate verification in ticketing system connectors
-  Housekeeper scripts (NXSL and SQL)
-  Improved REST API
-  Introduces new object class "Collector"
-  Downtime log controlled by EPP

Fixed issues:
-  NX-797 (Automatic reconnect of management console)
-  NX-1790 (Drag-n-dropped object are positioned to wrong place when map is scrolled down or right)
-  NX-1870 (Representation of float DCI that gets string data as input)
-  NX-1935 (Introduce hook script on map regeneration with ability to set link names)
-  NX-2006 (Remove example event templates (code 4000-4011) from database)
-  NX-2076 (Raw value should be always displayed as string)
-  NX-2292 (Automatic maps should not include nodes that are connected through a node that was excluded by filter script)
-  NX-2323 (Make parameters in all events named)
-  NX-2343 (Several changes in NXSL syntax in v 5.0)
-  NX-2375 (Use "varchar(max)" instead of "text" on Microsoft SQL Server)
-  NX-2403 (Add support for AES-192 and AES-256 in SNMPv3)
-  NX-2444 (On demand background external metrics)
-  NX-2455 (Ability to check TLS.Certificate.* for protocols with STARTTLS command)
-  NX-2481 (Add ability to manually poll network map generation)
-  NX-2507 (Add ability to cancel timers from NXSL)
-  NX-2520 (Remove "Channel name" selector from "Send notification" dialog)
-  NX-2523 (New agent metric Process.MemoryUsage (percentage of memory used by process))
-  NX-2524 (Option to disable threshold without deleting it)
-  NX-2525 (Add the ability to specify multiplier values in threshold)
-  NX-2526 (When editing a template with a DCI without instance to use instance - DCI becomes unsupported)

Hi, the pinboard seems to not work in the 5.0.0 version of the new desktop client (with 5.0 server)?  You can pin left/right however if selecting the pinboard and then going to the pinboard screen it is still empty.

Hello

Is NetXms no longer free starting with version 5?

Still free, why did you get this feeling?

Quote from: Egert143 on May 03, 2024, 08:54:52 AMHello

Is NetXms no longer free starting with version 5?

Hi,

is is still free and open source, we do not have plans to change that. What was changed is that some of the binary builds that we consider of being more enterprise level are not provided for free on our web site, and only available through support contract. Those builds are agents for AIX and Solaris, and server for Windows. You still can build them from source code though.

Best regards,
Victor

I was looking for the server installer for windows and saw that now support is needed for this. That is why i asked if it was no longer free.

is building windows installer for server from source complex task ?

Quote from: Egert143 on May 03, 2024, 09:08:56 AMI was looking for the server installer for windows and saw that now support is needed for this. That is why i asked if it was no longer free.

is building windows installer for server from source complex task ?

Depends on your experience of course Build itself is straight-forward - there is Visual Studio solution file in the root of source tree, it will handle all the builds. Tricky part is to get all the dependencies (openssl, libcurl, libssh, libjq, libmodbus, libmosquitto, libpcre, database client libraries, breakpad, libmicrohttpd). Some of those are for specific components only, which you can exclude from build if you don't need them.

But I think that's a real shame! I would be happy if a Windows version was still offered.

PLS!

Patch release 5.0.1 published (it fixes bug in database upgrade procedure).

Hello @all,

noticed that there are no more windows server downloads online, except for users with active support contract... Are there any announcement that i missed?

I never heard or read of this change. I only noticed this cause i take a look in the download section of the NetXMS website.

It would have been nice if you had announced the change a bit in advance, then everyone could have thought about how to deal with it...

Greetings
Marco

Quote from: Spheron on May 03, 2024, 04:01:33 PMHello @all,

noticed that there are no more windows server downloads online, except for users with active support contract... Are there any announcement that i missed?

I never heard or read of this change. I only noticed this cause i take a look in the download section of the NetXMS website.

It would have been nice if you had announced the change a bit in advance, then everyone could have thought about how to deal with it...

Greetings
Marco

Yes, I agree that we should have had announced it in advance. I will discuss it with the team and announce if there will be any changes to new policy.