NetXMS Support Forum

We're excited to announce the release of version 4.3 of NetXMS! This new version brings a bunch of new features and improvements, including:

- Python-style format strings in NXSL;
- Inline action scripts in EPP;
- The ability to set and delete custom attributes in EPP rules;
- Column display names in object queries can be set using column metadata;
- New agent metrics for file type and file content;
- A brand new "File Monitor" dashboard element.

We've also fixed bunch of bugs and made several other improvements, like correctly reading LLDP information from devices that only support LLDP-V2 MIB and improving object queries.

We've also made a slight change to our versioning system. Similar to before, releases are defined by a major and minor version (like 4.3 in this case) and all components with the same major.minor version number are guaranteed to work together. However, we're now hiding the build number for regular releases. The third number in the version will indicate an official patch release, with 0 being the initial release for that version. Any builds in between official releases will be denoted by a fourth number, which indicates the build number after the patch release.

Full change log can be found here: https://netxms.com/release-notes

Thanks,
The NetXMS Team

Hi all!

We just published new patch release for version 4.2 - 4.2.461. Changes since previous patch release:

- Improved dashboard element "status indicator"
- Improved SMSEagle notification channel driver
- Fixed random zero values returned by Linux agent for file system space metrics
- Fixed copy MAC in FDB table
- Fixed server certificate monitoring template
- Fixed issues:
        NX-2326 (Add parameter in log parser events that contains file name)
        NX-2346 (Unexpected SNMPv3 authentication failures)
        NX-2349 (NXSL executeAgentCommand crashing server)

Best regards,
Victor

Just updated dependencies in development branch, next patch release will include 8.0.31. But this connector is only used by reporting server when your database is MySQL, so if you are not on MySQL or not using reporting server you are safe anyway.

Best regards,
Victor

Hi,

You have to build those two libraries yourself from their sources.

Best regards,
Victor

Hi,

we will take a look at this and fix if it is a bug on NetXMS side. I've registered it as a bug: https://track.radensolutions.com/issue/NX-2346

Best regards,
Victor

For version 4.3 we have also added new metric File.Type, which returns 0 if file does not exist, 1 if it is a directory, 2 if it is a device, and 3 if it is a regular file.

Best regards,
Victor

Hi!

most likely server does not have certificate. If this is the case than you can safely ignore this error, or delete problematic DCI.

Best regards,
Victor

We just published patch release 4.2.433. It fixes critical bug in release 4.3.432 (non-working hook scripts).

We just published patch release for version 4.2 - 4.2.432. Changes since previous release:

- Driver for Juniper Networks devices retrieves product information from vendor MIB
- Empty source/tag is processed as match any source/tag for Windows Event Log and syslog parser
- Configurable maximum message size for client connections
- "Follow location" option for web services
- Fixed server crash after DB connection loss
- Fixed server deadlock within topology poll
- Fixed web application property reading from JNDI and properties file
- Fixed issues:
        NX-2278 (Support for hexadecimal encoding of OCTET STRING in nxsnmpset)
        NX-2298 (Alphabetize Source Objects in Event Processing Policy)
        NX-2315 (Chained import in NXSL is not working)
        NX-2321 (History for a Table DCI value shown as empty)
        NX-2333 (Data collection error thresholds show up as "error(1) < 0")

Best regards,
Victor

It is known issue, will be fixed in upcoming patch release.

Best regards,
Victor

Обновил nxsnmpset, теперь у него появился ключ -H для указания hex строки. Будет в следующем патч релизе 4.2.

I've updated Juniper driver to use this MIB if available. Changes will be included into next patch release.

Best regards,
Victor

New Windows installer just published.

Best regards,
Victor

Quote from: lindeamon on October 22, 2022, 10:41:38 AMthank you for all the hard work and for giving us this awesome piece of software.
when can we expect the completion of the new UI  ?

Functionality wise it is mostly complete, most likely we will move remaining functionality during 4.2 patch releases.
As for UX (interaction with views, menus, etc.) - we are still experimenting, and major changes are still possible. Feedback from users also very important.

We just published repackaged Windows installer for web UI (version 4.2.398) with Jetty 10 inside.

Best regards,
Victor