NetXMS Support Forum

Hi,

These are now executeAgentCommand and executeAgentCommandWithOutput methods of Node class
https://www.netxms.org/documentation/nxsl-latest/#_instance_methods_18

In overall we tend to migrate from functions to object methods - this make a cleaner code and we can also list methods available on an object - see an example here: https://www.netxms.org/documentation/nxsl-latest/#class-class

Typically full DCI description is quite long and inconvenient to be used on links, that's why it's not displayed there by default.
What we have instead is so called format string, which can be seen in properties of a data source. Format string can contain any text, so you can just put description of your DCI there. Placement of DCI value is defined by java macros. See docs for information on this: https://www.netxms.org/documentation/adminguide/visualisation.html#adding-links-between-objects

To have a table with values on a dashboard we have the following options:
- Object query
- DCI summary table
- We can use script to build a Table DCI and display that on the dashboard

But I still do not understand how bar graphs and line graphs should work - do you want them to show data from 3 "worst" nodes?

For expansion - I've registered a ticked to add expand/collapse buttons: https://track.radensolutions.com/issue/NX-2745

Grouping by software package looks cumbersome - e.g. some software packages tend to have version number in the name, e.g. jdk-17... and jdk-21..., could be desirable to join them somehow... So unless it's a sponsored development we don't have resources available to go into this.

But, to mention, software package information is accessible from NXSL, so it might be that for some usecases you can just script something.

If I correctly understand your use case, Object Query can help: https://www.netxms.org/documentation/adminguide/visualisation.html#object-query

A bit later I can prepare some example that would pull DCI value from nodes.

Try removing quotes around the question mark:

ConfigurableQuery = Database.Data:id1:Custom data:SELECT `name` FROM `test` WHERE `description` LIKE ?;

It's ok, logs are good. The thing that it needs is WebView2 - https://developer.microsoft.com/en-us/microsoft-edge/webview2

What's changed from previous version is that in 5.2. we have what's new screen that opens on the start. And current code does not check properly if WebView2 is available - this will be fixed.

Is this log from Windows Server 2016 system? Can you also show one from Windows 10?

Client writes log in \.nxmc4\nxmc.log in user's home folder. Are there any errors in this file?

Can you show screenshots of how the DCI is configured (just the General page of DCI properties) and where exactly the "Display Name" is empty?

You can use Tools -> Find Object -> Query with the following to get all unmanaged nodes:
type == NODE and status == Status::UNMANAGED
 

 

You can try to run agent with DebugLevel = 6 in it's config - actual query and detail of execution should be visible in the log. Pls share the log part related to execution of the query.

Nice to hear that

Problems with compilation are probably because libcurl library is now used for a few things, smtp in particular. But it's better just to use packages.

You can install netxms packages right on the same system, just remove systemd unit or whatever way the old server and agent were started by.

nxagentd.conf will be in /etc, currently it's probably the same
server files, images are under /var/lib/netxms/, if compilation was with default prefix, then currently it's same location
and the database, with which new binaries will work same way and the old ones


Export-import is also possible, this will export all the configuration, without logs and collected data:

nxdbmgr -s -Z all -e hardware_inventory -e software_inventory export backup.sql

And to import on the new system:

nxdbmgr import backup.sql

And you'll need to copy conf file and folders I've mentioned above. 

Any reason why you compile it yourself? We have packages for Ubuntu.