We finally published NetXMS version 6.0. It is major release with lot of changes. Most notable changes are:

- Integrated AI assistant and AI agent
- AI-powered anomaly detection
- Built-in basic incident management
- Legacy UI is finally dropped
- Data collection now uses millisecond timestamps, allowing multiple values per second

Important notice: database upgrade will convert timestamps for collected data into milliseconds, and that can take significant amount of time, so plan upgrade accordingly.

Full change log

-   Integrated AI assistant and AI agent
-   AI-powered anomaly detection
-   Built-in basic incident management
-   Improved SSH support
-   Event processing rules with empty filters are skipped (instead of "match all" behavior)
-   Instance discovery for push DCIs
-   Any NXSL object can be converted to JSON
-   Optional function calls in NXSL
-   New NXSL operator "has" for simplified bit field tests
-   Changed NXSL variable lookup priority (local variables now have higher priority)
-   New NXSL keyword "local" for explicit creation of local variable
-   NXSL functions and string methods for fuzzy matching
-   New methods in NXSL classes JsonObject and JsonArray to set value with explicit data type
-   Improved web service call interface in NXSL
-   Removed unused 'Objects.Security.ReadAccessViaMap' server configuration variable
-   Node decommissioning
-   Fixed unique constraint failure for network\_map\_deleted\_nodes table
-   Added SNMP Walk button to MIB Explorer with the option to walk OIDs not present in NetXMS MIB database
-   Integration with HashiCorp Vault for secure credential management
-   Server database password can be provided via external command
-   Added lock for database inline upgrade
-   DCI option to interpret unsupported state as data collection error
-   New internal table Server.Queues
-   Objects can be marked as "hidden"
-   Drill-down option for dashboard element "Status indicator"
-   Drivers for Planet LAN switches
-   Drivers for Planet industrial switches
-   Fixed "Go to DCI" action
-   Data collection uses millisecond timestamps
-   Dropped support of AIX 6.1
-   Reworked configuration export/import to use JSON instead of XML; XML import is retained for backward compatibility
-   Fixed deadlock in session termination caused by DCI force poll reference leak
-   Fixed interface IP address access by adding lock to prevent use-after-free

Fixed issues

-   NX-119 (Add support for drops counters on interfaces)
-   NX-352 (Use display hint from MIB files in server and command line tools)
-   NX-484 (Open Event Log from Event monitor)
-   NX-507 (Show effective ACL for object)
-   NX-531 (Use ENTITY MIB for physical port mapping)
-   NX-600 (MikroTik authentication failure alarms from syslog)
-   NX-616 (nxdbmgr should detect missing proxy node for item)
-   NX-660 (Scroll network map by dragging on empty space)
-   NX-753 (Interface speed mismatch or under-utilization detection)
-   NX-879 (Agent explorer (like MIB explorer))
-   NX-983 (Event details accessible from event monitor)
-   NX-1072 (SNMP context support in data collection)
-   NX-1293 (Insert data with timestamp from NXSL)
-   NX-1439 (Dashboard widget "Table" should notify user DCI is in error state instead of showing empty table)
-   NX-1443 (Merge threshold/table threshold rules in default EPP)
-   NX-1795 (On TimescaleDB when DCI storage class changes historical data should get copied to new storage class)
-   NX-1826 (Graph option to not join lines if time between is over a specific value)
-   NX-1872 (DCI Table column ordering)
-   NX-1917 (Add "Copy SQL" button to Log viewers)
-   NX-1979 (Ability to set DCI into maintenance mode)
-   NX-2160 (Option to not show default columns in Find Object -> Query results)
-   NX-2188 (Add search/filter in network maps)
-   NX-2202 (Add access to alarm's related event list from NXSL)
-   NX-2246 (Add report retention and housekeeper in reporting server)
-   NX-2344 (Decommissioning for nodes)
-   NX-2398 (Add method for node and interface setPollCountForStatusChange)
-   NX-2437 (Ability to change MAC address on an interface)
-   NX-2447 (Add ability to instance-discover notification channels and server queues)
-   NX-2462 (Add "value with multipliers and units" column in DCI history view)
-   NX-2496 (Add methods to Tunnel class for binding new tunnels)
-   NX-2497 (Add option "go to DCI" for alarms that are related to a DCI)
-   NX-2558 (Add separate access right to manage agent policies within templates)
-   NX-2573 (Event template editor window is not resizable)
-   NX-2579 (User is not able to create node without having access on whole zone if zonning is enabled)
-   NX-2588 (Show unsupported DCIs by default)
-   NX-2612 (EPP rule import does not warn that a rule is referring missing event)
-   NX-2638 (After disabling a DCI in template there's no message with apply button is displayed)
-   NX-2643 (Add function to read list of available packages (and versions) in package manager from NXSL)
-   NX-2655 (Add an option to select sort column and ASC\\DES for Table DCI on Dashboard)
-   NX-2677 (Remove support of \ in macro processing)
-   NX-2697 (Improve management of authentication tokens)
-   NX-2709 (Automatically add scripts mentioned in macros in configuration export view)
-   NX-2710 (Traffic graphs for interface on overview)
-   NX-2722 (Add attributes of class User to Alarm and AlarmComment class)
-   NX-2736 (NXSL function to return DCI values as (timestamp, value) tuples)
-   NX-2743 (Do not execute EPP rule if it has no filters)
-   NX-2747 (Add threshold id to event parameters)
-   NX-2756 (Events are not correlated across server restarts)
-   NX-2757 (Add view deactivation on perspective change)
-   NX-2758 (NXSL function to find all DCIs of a node that have specific related object)
-   NX-2763 (Dashboard charts ignore multiplier setting in DCI)
-   NX-2771 (Display current grace period for automatic template removal in template property page)
-   NX-2773 (Rework threshold event repetition to exact interval)
-   NX-2774 (Allow to specify column for instance-name for instance discovery from a table)
-   NX-2778 (Logwatch should save file position in agent DB)
-   NX-2779 (Add instance value as event parameter)
-   NX-2789 (Add separate boolean attributes to represent state bits in NXSL network object classes)
-   NX-2791 (Keep timestamp of when interface peer information was last updated)
-   NX-2792 (New way to create links on custom map that would set link interfaces from topology)
-   NX-2803 (Repeat interface and network service events when node goes out of maintenance)
-   NX-2810 (Log parser metrics work correctly if only one file is given to the parser)
-   NX-2811 (Data collection edit mode displayed incorrectly when going from a template to a node)
-   NX-2814 (Auto link objects should allow object linking even if non object elements are selected)
-   NX-2815 (Leave disabled "Link objects" option in menu when multiple objects are selected)
-   NX-2817 (Rename MapLinkStyle:: constants)
-   NX-2818 (Investigate and update MySQL monitoring subagent)
-   NX-2823 (Drill-down dashboard not opening)
-   NX-2824 (Use float for delta per second or minute calculation)
-   NX-2826 (Automatic dashboard creation from template)
-   NX-2830 (Add option to export-import syslog and windows event processing rules)
-   NX-2839 (DCI "Query" button fails silently on error)
-   NX-2840 (Add parameterized metrics for structured metric provider)
-   NX-2841 (Add ability to monitor and control systemd services on Linux)
-   NX-2842 (Pinned line chart changes time period also for original chart)
-   NX-2844 (Header with DCI name, [DCI metric] and units in DCI history view)
-   NX-2854 (Ability to specify default column type for agent external table)
-   NX-2857 (Limit notification channel message queue and create event when limit is hit)
-   NX-2858 (Add debug console command to clear notification channel queue)
-   NX-2863 (Stop list for ports)
-   NX-2869 (Local variable should have priority over object attributes in object query)
-   NX-2870 (NXSL keyword to explicitly declare variable as local)
-   NX-2871 (Add SYS\_IF\_UNMANAGED event)
-   NX-2873 (Rename "Full configuration poll")
-   NX-2877 (Show "What's new" only to specific users and only once)
-   NX-2879 (Add GUID support in EPP editor filter)
-   Nx-2882 (Ask whether to delete or detach DCIs on template deletion)
-   NX-2884 (Use character limit for varchar fields on Oracle)
-   NX-2887 (Use DCI multiplier configuration to format DCI value in DCI summary tables in Grafana Infinity API)
-   NX-2889 (New DCI option: save only every n-th sample)
-   NX-2891 (Add lastAlarmId attribute to Event class)
-   NX-2892 (callWebService() does not set errorMessage if EnableWebServiceProxy is not enabled)
-   NX-2894 (DCI description not appearing in Data Source table in Saved Graph)
-   NX-2895 (Action with event and without alarm using DCI macro crashes server)
-   NX-2896 (Unified DCI template matching for context dashboard elements)
-   NX-2902 (In the notification channel, when using telegram and Proxy and DisableIPv6 = true, the server queries DNS IPv6 AAAA)
-   NX-2903 (Add support for # character in cron format)
-   NX-2904 (System.IO.DiskTime calculated incorrectly on Windows)
-   NX-2905 (Report Windows Store Installed Applications in Software Inventory)
-   NX-2906 (Values sent by nxapush should be cached in agent DB if connection to server is not available)
-   NX-2908 (Object/Tag should be displayed as <context> for DCI template elements of dashboard status indicator)
-   NX-2912 (Last known table value is shown instead of error when table DCI is in error due to connectivity loss to agent)
-   NX-2914 (DCIs from cluster are not reapplied to nodes under cluster on housekeeper run)
-   NX-2915 (DCIs with template <unknown> left on nodes when a cluster is deleted)

I have upgraded the server and agents from 5.2.8 to 6.0.0 succesfully.

Also, deployed the Web interface (war) 6.0.0.jar on tomcat9 with jre 17, but not working.

NetXMS 6.0 uses newer version of GUI framework which requires newer version of servlet API. Please try tomcat10

Important notice
If you have relatively large database (starting with few hundred of nodes or few thousands of DCIs or long retention time) - delay upgrade to 6.0 until patch release 6.0.1, which we plan for Monday. Unfortunately, current DB migration procedure turns out to be inefficient for bigger databases, so we are working on an updated one.

Quote from: Filipp Sudanov on February 06, 2026, 05:16:34 PMNetXMS 6.0 uses newer version of GUI framework which requires newer version of servlet API. Please try tomcat10

Although Tomcat 9 came pre-installed with Alma Linux 9, I tried manually installing Tomcat 10 and the web interface worked normally.


Please note that the administrator documentation does not contain detailed requirements for version 6.0.

https://www.netxms.org/documentation/adminguide/installation.html#web-management-client

Thank you for the new release. Is it possible to again provide a statically linked binary of the agent for Linux x86_64 as a download (like nxagent-5.2.8-linux-x86_64-static.tar.gz)?

Quote from: batnator on February 09, 2026, 05:36:05 AMThank you for the new release. Is it possible to again provide a statically linked binary of the agent for Linux x86_64 as a download (like nxagent-5.2.8-linux-x86_64-static.tar.gz)?

I think yes, we will bring those back in a few days. Can you explain a use case for those? I'd think that nowadays agents mostly deployed from deb or rpm packages.

Quote from: Victor Kirhenshtein on February 09, 2026, 11:30:06 PM

Quote from: batnator on February 09, 2026, 05:36:05 AMThank you for the new release. Is it possible to again provide a statically linked binary of the agent for Linux x86_64 as a download (like nxagent-5.2.8-linux-x86_64-static.tar.gz)?

I think yes, we will bring those back in a few days. Can you explain a use case for those? I'd think that nowadays agents mostly deployed from deb or rpm packages.

My firewall is based on a hardened Linux system that doesn't use any deb or rpm-based package management. It sounds great that you're planning to make a statically linked version available again; that saves me from having to set up a complete firewall development stack just to compile the agent as an add-on from source.

Hey Victor will the change in idata/tdata timestamp to millisecond impact the REST API or NXSL dci values? i.e. will we see millisecond timestamp there as well or will we only see change in db?

Thank you for the update.  Any ETA when the console, agent, etc will have a patched openssl (CVE-2025-15467).

Thanks in advance!

Quote from: johnnyva on February 23, 2026, 11:42:37 PMHey Victor will the change in idata/tdata timestamp to millisecond impact the REST API or NXSL dci values? i.e. will we see millisecond timestamp there as well or will we only see change in db?

New REST API (webapi module) - it is using ISO 8601 format for timestamps which allows milliseconds (although 5.x did not set millisecond part), any decent ISO 8601 parser should handle milliseconds correctly.
Old REST API (Java app) - should be unaffected.
NXSL - all timestamps for collected data are now in milliseconds.

Best regards,
Victor

Could you please update docs pages (NXSL and admin guide) for where unix timestamps are in milliseconds vs seconds.  It feels like this could get confusing if there is a mix of unit when unix timestamp is referred to.

I'm expecting that this (https://www.netxms.org/documentation/nxsl-latest/#class-datapoint) would be the only place that would have changed from seconds to milliseconds because this is the only place to get list of DCI datapoints including timestamp right?

@victor Also, the timestamp conversion will be a background task after netxms server/db upgrade?  If so, how will nxsl/rest api present the timestamps when not all timestamps have been converted?  Will we have a mix of seconds and millisecond timestamps or will netxms server convert seconds to milliseconds even if the db entry has not been updated by the background task yet?

Quote from: johnnyva on March 02, 2026, 11:04:34 PM@victor Also, the timestamp conversion will be a background task after netxms server/db upgrade?  If so, how will nxsl/rest api present the timestamps when not all timestamps have been converted?  Will we have a mix of seconds and millisecond timestamps or will netxms server convert seconds to milliseconds even if the db entry has not been updated by the background task yet?

Yes, conversion is a background task (but you should upgrade straight to 6.0.4), server will do conversion in background. Internally server renames idata tables, create new empty tables, and gradually moves data from old to new with conversion. So API will not see incorrect timestamps, but for some time after server start you will not see older data.