NetXMS Support Forum

General => Announcements => Topic started by: Victor Kirhenshtein on February 10, 2021, 06:01:22 PM

Title: NetXMS 3.8 released
Post by: Victor Kirhenshtein on February 10, 2021, 06:01:22 PM
Hi all!

NetXMS version 3.8 is released. It is minor release that provides some performance and usability improvements, as well as updated reporting server. Full change log since version 3.7:

- Improved reporting server
- Support for key based SSH authentication
- Web service proxy function in core agent now disabled by default
- Only HTTP and HTTPS are allowed in web service URLs
- Context configuration removed from global log parsers configuration views in UI
- New NXSL functions PollerTrace and SendNotification
- New method setNamedParameter in NXSL class Event
- Fixed bug in subnet mask correction
- Added Topology.RoutingTable internal DCI table
- Fixed bug on node creation
- Fixed issues:
        NX-1437 (Show tunnel connection time in tunnel manager)
        NX-1775 (Add deactivation event to list of thresholds in DCI properties)
        NX-1988 (Show full user name in user selector dialogs)
        NX-1991 (Incorrect handling of HTTP and communication errors when collecting data from web services)
        NX-1992 (Properly parse : in web monitoring parameter name)
        NX-1994 (Handle multiple agents connecting back to same node)
        NX-1999 (Make routing table available as internal table)
        NX-2000 (Snooze timer in EPP to avoid repeating actions)
        NX-2001 (Add ability to put trace messages from hook scripts to text output of status/conf/etc poll)
        NX-2004 (/objects/<container_id> REST API endpoint against container object returning error 46 - multiple JSON fields named flags)

Best regards,
Victor
Title: Re: NetXMS 3.8 released
Post by: lindeamon on February 11, 2021, 08:24:17 AM
thank you victor and all for the great work !!!
when do we expect to see version 4 ?
Title: Re: NetXMS 3.8 released
Post by: lweidig on February 11, 2021, 06:19:07 PM
Totally agree with lindaemon that this has and continues to be an excellent product!

It does not appear the Ubuntu repositories (maybe others) have not bee updated, any ETA?
Title: Re: NetXMS 3.8 released
Post by: Victor Kirhenshtein on February 11, 2021, 06:45:31 PM
Thank you!

We have unexpected issues with deb packages, working on it.

Best regards,
Victor
Title: Re: NetXMS 3.8 released
Post by: tanero on February 15, 2021, 08:30:22 AM
- Web service proxy function in core agent now disabled by default
- Only HTTP and HTTPS are allowed in web service URLs


Please could you explain, how can I enable web service check from agent ?

After upgrade from 3.7 to 3.8, my web service dci polling has been stopped. I wonder if it is config changed issue ?
Title: Re: NetXMS 3.8 released
Post by: Victor Kirhenshtein on February 15, 2021, 10:14:17 AM
Hi,

you should add to config file of your agent the following line:

EnableWebServiceProxy = yes

This change was done for improving security. Before 3.8 read access to agent allows you to do port scan (by requesting URLs with different service types and port numbers) and even local file access (using file:// URLs).

Best regards,
Victor
Title: Re: NetXMS 3.8 released
Post by: tanero on February 15, 2021, 10:52:52 AM
Quote from: Victor Kirhenshtein on February 15, 2021, 10:14:17 AM
Hi,

you should add to config file of your agent the following line:

EnableWebServiceProxy = yes

This change was done for improving security. Before 3.8 read access to agent allows you to do port scan (by requesting URLs with different service types and port numbers) and even local file access (using file:// URLs).

Best regards,
Victor

Thanks for reply, I have added above config to the agent file, but realized still not recieving polling data. 

But after adding this config to master server's agent file, polling is started. 

Is that result normal ?
Title: Re: NetXMS 3.8 released
Post by: Victor Kirhenshtein on February 15, 2021, 12:40:38 PM
You should add it to config of agent that is used for web service query. By default it is local agent on NetXMS server machine.

Best regards,
Victor