NetXMS Support Forum

We plan to pack a JRE along with the console to simplify all this.

You mean when setting log file as syslog, right? (LogFile = {syslog})

Replicated that. It's related to interface loading optimization that was done a few versions ago - information about all interfaces is not being loaded on console start to make the startup faster.

В следующем релизе планируется паковать нужную версию JRE вместе с nxmc

The report engine used is Jasper Reports: https://en.wikipedia.org/wiki/JasperReports

An example of report could be found, e.g., in this forum message: https://www.netxms.org/forum/general-support/reporting-server-4315/msg20117/#msg20117

For Debuan/Ubuntu the best practice is to install and upgrade by means of OS package manager (apt / apt-get). There are tools to automate deployment of packages like Puppet, Chef, etc.

Installing using apt and upgrading from NetXMS Package Manager should not be done - location of binary/configuration/log file could be different and there'll be mess on the target system.

Попробуйте 3.8, она вышла только что

Еще можно указать в nxmc.ini:

-vm
/usr/lib/jvm/java-11-openjdk-amd64/bin/java

Опция -vm должна быть после других опций Eclipse ( -product, --launcher.* и т.д.), но до -vmargs т.к. они напрямую передаются в JVM.
https://wiki.eclipse.org/Eclipse.ini

Try checking alarm log (View -> Alarm log) to see what was happening - what was the event that triggered the alarm and what is the alarm key.

Ah, I was thinking of .deb packages.

Generic builds are limited to use only dependencies that are available everywhere. That's why curl, ssh and asterisk stuff is not included. Web services are depending on curl.

We will try to prepare a build that would be suitable for Centos 7/8.

The basic approach is data collection via SSH - you just create a DCI with SSH origin, its running a command on the remote system and saves first line of output as DCI value.
https://www.netxms.org/documentation/adminguide/ssh-monitoring.html

Please inform, if this suits your needs.

You can try using Custom schedule and specifying exact seconds for various DCIs: https://www.netxms.org/documentation/adminguide/appendix.html#cron-format

Other possible approach could be network traffic throttling: https://man7.org/linux/man-pages/man8/tc-tbf.8.html

Which exactly version are you installing? Is it from packages or you compiled?

In NetXMS alarms that are present on a node affect node status.

Looks like your EPP does not have a rule to automatically terminate node down alarm when node comes back up (see screenshot of default EPP configuration on that).

What's currently in alarms for this node (right click on node -> alarms)?