NetXMS Support Forum

Hi all!

New stable version of NetXMS - 3.1 - is officially released. Changes since previous release:

- Added custom attributes inheritance
- Can enable usage of ICMP ping on primary IP address during status poll
- Macro expansion in DCI polling interval and retention time values
- New attribute "isInMaintenanceMode" in NXSL class "NetObj"
- New attributes "dci" and "dciId" in NXSL class "Event"
- New method "forcePoll" in NXSL class "DCI"
- New NXSL functions "ExpandString" and "LoadEvent"
- New methods "correlateTo" and "expandString" in NXSL class "Event"
- New method "expandString" in NXSL class "NetObj"
- New hook "Hook::EventProcessor" that is called for each event before passing it to EPP
- Added global array $ARGS in NXSL scripts for simplified access to script arguments
- Added NXSL constants NXSL::VERSION and NXSL::BUILD_TAG
- Interface object names can be expanded from actual interface names using macros
- Notification channel driver for Telegram
- Notification channel driver for Microsoft Teams
- File delivery policies for agents
- Improved automatic IP topology maps
- Added physical links inventory for node interfaces and patch panels
- Fixed issues:
        NX-1674 (Initiate DCI forced poll from NXSL)
        NX-1675 (Context menu for containers and "Service Root" shows "Create sensor" twice)
        NX-1681 (In NetXMS console refresh from view pull-down menu is not working on Data Collection Configuration)
        NX-1686 (User Agent system tray menu covered by Windows system tray expanded hidden icon menu)
        NX-1687 (User agent system tray menu closes when you click out of it)
        NX-1691 (Network map link bend points seem a bit broken in 3.0)
        NX-1694 (Russian language problem in Windows log)
        NX-1706 (Compose interface name from the actual name and a suffix)
        NX-1708 (Event tags in log file monitoring are not represented in UI)
        NX-1710 (Add serealized to json event to event log)
        NX-1712 (Add support for reading WMI query result as list or table)
        NX-1713 (Object tool for container should be shown if it can be executed on at least one node)
        NX-1717 (Alarm pop-ups apear only on console start, afterwards are not shown)
        NX-1719 (File monitoring with rescan is not matching text past 4KB of the monitored file)

Best regards,
Victor

Hi,

if you want data on map links, right click on a link, select "Properties", then "Data sources", and add DCIs you want to display on that link.

Best regards,
Victor

I also highly recommend to upgrade. Older client versions had issues dealing with some tile servers, including default one.

Best regards,
Victor

Hi,

if you don't have any data collection configured idata tables should stay empty. If you don't want them to be created at all you can try to switch database into single performance data table mode:

1. Stop netxmsd
2. Run the following query:

UPDATE metadata SET var_value='1' WHERE var_name='SingeTablePerfData';

3. Drop any existing idata_nnn and tdata_nnn tables (tables "idata" and "tdata" should stay).
4. Start netxmsd

Please note that single table mode was intended only for TimescaleDB. Theoretically it should work on any DB, but you are on your own here!

Best regards,
Victor

It is bug in UI. What version you are using? Is it web or desktop console?

Best regards,
Victor

Hi,

turns out that there is no way to get this object from NXSL. I'll add lookup functions in next release.

Best regards,
Victor

Hi,

I definitely recommend to upgrade your server and UI to 3.0. It will work with 2.2.8 agents on Raspberry. We have build environment for RPi mostly ready, I think RPi agent will be published as part of next release.

Best regards,
Victor

Where exactly it is not saved? In node properties? Or in global settings?

Hi,

currently not.  I think we will implement it though.

Best regards,
Victor

Hi,

you can create internal DCI for parameter "Dummy" and use transformation script like


return $node->ipAddr;


Best regards,
Victor

Это какой-то косяк в документации. Драйвер для Telegram войдет в релиз 3.1 (мы планируем на этой неделе сделать).

This looks like a bug in configure script - it is made with assumption that library files always installed under PCRE prefix /lib. Seems to not be the case on SUSE. I'll update configure script.

Best regards,
Victor

That means that libpcre was not properly built or installed. Are you sure that there were no compiltation or installation errors? What files are present in /opt/pcre/lib?

Best regards,
Victor

Very strange. Please show output of command

file /opt/pcre/lib/libpcre32.so*

and

ldd /opt/pcre/lib/libpcre32.so

Best regards,
Victor

Похоже что сервер застрял на опросе новых узлов. Какая версия NetXMS?