NetXMS Support Forum

The could be an issue that first SSH.Command since agent start is failing (https://track.radensolutions.com/issue/NX-1852), but is should start working when polled again.

Regarding the timestamps in the future - there are basically a few scenarios how that could happened:
- time has jumped on netxms server into the future and then back (so some values have recorded with future times during that time)
- more probably - time problem on some agent with cache mode = on
- not sure, but probably - time problem on netxms agent running in proxy mode
Monitoring time on all agents is advised.

For the links on the map - does the object with ID=842468 exist? (you can search for ID in object tree with # prefix, e.g. #842468)

We will add checking for this situation to nxdbmgr. You can track the progress in this issue: https://track.radensolutions.com/issue/NX-1851

libvirt is not well supported on Windows and only old version is available.
I'd advise to use a separate linux system with netxms agent and libvirt.

Absolutely, please check NetXMS docs on that: https://www.netxms.org/documentation/adminguide/ssh-monitoring.html
Make sure you add ssh.nsm subagent to the configuratio file of netxms agent running on your netxms server and restart the agent afterwards.

Just tried compiling 3.3.285 on a fresh Centos 8.1

I had to install the following dependencies:
yum install make gcc-c++ openssl-devel libcurl-devel libssh-devel pcre-devel libpq-devel


Have not figured out what package to install for mosquitto, so disabled it in confgiure:
./configure --with-server --with-pgsql --with-agent --disable-mqtt


Please check if you have all dependencies installed and try again.

If it's still in that condition, can you run this script to get thread statuses:
https://github.com/netxms/netxms/blob/master/tools/capture_netxmsd_threads.sh

Please run it twice with about 1 minute interval and attach the files it creates in /tmp.
The script requires gdb to be installed.

Not sure, if that approach would suit your situation, but here's an alternative

DCI object has attribute lastPollTime. That's the time stamp of last time that DCI got data. You can read this value in transformation script of your "primary" DCI. When delayed data would be coming to the server, this attribute will show correct timestamp of each incoming datapoint.

The idea is that you can configure your "secondary" DCIs as push DCIs. And implement the logic in the transformation script of the "primary" DCI.

E.g. if a new hour has started, you can calculate the average of the "primary" DCI and push it to the "secondary". Some more logic requred to do it only once - you can use a custom attribute and store last time there.

Can you also show the screenshot of configuration of this DCI - first page - "General"

Thank you for reporting.
The ThreadPool DCIs are failing because you have only one SYNCER process configured (default setting) - in this case thread pool mechanisms are not used.
Server.Heap ones work only if server was compilled with jemalloc.

In coming 3.3. version out of the box templates were updated to fix these issues.

First parameter of CountEx should be process name which is actually "node".
Try something like this:
Process.CountEx("node", "\/kibana\/")

The thing is that the .bat file is not an executable as such, it's being executed by cmd.exe. And ExternalParameter needs an actual executable.
Running cmd.exe /C <your_bat_file> should probably to the job.

No such functionality is currently implemented. It could be a valid approach, but such averages tend to look differently then original data - e.g. spikes are smoothed. It could be possible to keep 3 values - min, max and average, but then it complicated the system and requires more development effort.
Since storage is quire cheap these days, a simpler approach is just to store more data - with Postgres time scale DB it's possible to delete old data with minimal load onto the database.

There is Process.CountEx() metric, that should allow to filter processes by the command line that was used to launch them.
https://www.netxms.org/documentation/adminguide/appendix.html#process-countex

You can find the command line by running
px fax

Filtering is done with the help of regular expression. You can test your regular expression here: https://regex101.com/

ExternalParameter is able to search in path, but requires exact executable name with extension. On the contrary, ExternalParameterShellExec calls shell and shell is able to find an executable even without extension (but I am not sure, if it is present in 1.0.13).