NetXMS Support Forum

Если нода находится в конкретной зоне, то она будет ходить через прокси который(ые) указаны в свойствах этой зоны.

А в настройках дискавери можно указать конкретную зону для active discovery, тогда ноды при их нахождении должны сразу оказываться в правильной зоне.

Yes, for time being it's file delivery policy, not file removal policy. Could be nice thing, but development resources are limited and there are more important features to work on, so probably only with sponsored development.

It's probably possible to add files with 0 size - this will at least delete contents of files.
It's possible to configure action on agent that would do deletion of files.
And, also requires quite some effort - nxshell / java app can use file manager api to talk to agent nodes and to the deletion.

There's still no easy way. Theoretically there could be an option to set source node from nxsl (and may be some hook script to set this right when template is applied). And there are many other things which can not be done from nxsl, so there's a lot of work to improve that.

So yes, it's possible to configure Script DCIs and do data collection that way.

Or another possible workaround is to have nxshell script that is executed as server's action and that script would change source node.

To mention, tables now can work in provider mode - there's new syntax for defining tables in agent config, what we need there is PollingInterval parameter.

Also, did you check if Web Service functionality could do the job for you? It's possible to use that from NXSL scripts.

I actually did not know that there's python subagent, judging by number of commits it's not actively developed, will check with developers in a while on it's status.

There's no option to clear history from the GUI, but you can delete data from database.

You need to stop server process prior to deleting from the DB!!!

The table you need are these two: BUSINESS_SERVICES_DOWNTIME, BUSINESS_SERVICE_TICKETS. First keeps downtime records, second keeps tickets which are displayed at the bottom when viewing a business service.

Document describing the DB is here:
https://www.netxms.org/documentation/datadictionary-latest/#t-business-services-downtime
https://www.netxms.org/documentation/datadictionary-latest/#t-business-service-tickets

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?