NetXMS Support Forum

Currently there is no out of the box functionality for that. It would be nice to have, but it depends of available development resources.
And the other question is how this should be implemented. Should we compare the actual value with average for, say an hour? Or with average value one day ago? Or with average on the same day of week or last business day?

First of all, you can try mean deviation threshold, it probably should increase if the value drops significantly. Number of samples in this case is the time during which the mean deviation is calculated. You need to experiment on this.

The other approach is to have two DCIs. First is collecting data as usual. Second is scheduled, e.g. every 10 minutes (it should not be too frequent to avoid producing load on the system), calculates average value of the first DCI for a period of time and stores it. First DCI then has script threshold that compares actual value with the average value. This script threshold can be quite advanced - compare value 24h ago, etc...

Please give an update how you implement this for you.

Hi!

Let me comment the steps that you've performed.

1) Part starting from tar zxvf netxms-3.5.90.tar.gz
You did compilation from sources here. For Ubuntu it's actually not needed, since we provide packages (which allow to install/upgrade software via apt-get)

2) Part starting from wget http://packages.netxms.org/netxms-release-latest.deb
If you look in the documentation, there are two sections there - "Using netxms-release package" and "Manually".
Only one of these was meant to be performed and the recommended is first one.
You can delete the last line in /etc/apt/sources.list.d/netxms.list that was added by steps from "Manually" section, but it's probably not causing problems (at least, for now).

3) Now, the reason for the error: Your database has format version 35.15, but server is compiled for version 34.16
When you did installation from sources, you used netxms-3.5.90.tar.gz., so it's version 3.5.90. And you did /usr/local/bin/nxdbmgr init there, so the database was initialized for that version.
But when you did install from packages, you got previous netxms version, because 3.5.90 was not available in packages yet (it was just released on that day and the packages were still prepared).

As of today, you can do
apt-get update
apt-get upgrade

and you should get 3.5.90 from packages. You can check package versions by running
dpkg -l | grep netxms

When you have 3.5.90, chances are that netxms will just start. But I am not sure about that, since you had
/usr/local/bin/nxdbmgr: error while loading shared libraries: libnxdbmgr.so.35: cannot open shared object file: No such file or directory
error when initializing the database.

So it's recommended that you delete your netxms database, recreate it and initialize it:
echo "DROP DATABASE netxms;" | mysql -u root -p

echo "CREATE DATABASE netxms;" | mysql -u root -p
echo "GRANT ALL on netxms.*to 'netxms'@'localhost' IDENTIFIED BY 'PaSsWd';" | mysql -˓→u root -p

in netxmsd.conf you have some old way of specifying database driver, please specify this way (a proper file example usually installs when installing package, but you already had this file, so it was not overwritten):
DBDriver=mysql.ddr

Then initialize the database - you also had old way of doing this, currently you should do just:
nxdbmgr init

Just tried on ubuntu 18, netxms-dbdrv-mysql is available there. What's your ubuntu version?

Поправим в следующем релизе, пока что попробуйте скачать https://netxms.org/download/releases/3.5/nxmc-3.5.90.war и положить его в  C:\NetXMS\WebUI\nxmc\nxmc.war

Hi!

There is an option called tunnel, when agents are establishing connection to NetXMS server. Connections are performed to port 4703 (configurable in server configuration parameters), so you need to open this port on the router where your server is running.

Configuration is a bit tricky - you need to create security certificates, just follow the sequence in the documentation:
https://www.netxms.org/documentation/adminguide/server-management.html?highlight=tunnel#server-configuration-for-agent-to-server-connection-tunnel-connection

Сделали изменения, в 3.5. должны поддерживать русские имена баз и пользователей.

Please share log of management console - it's located in user's home folder in .nxmc/data/.metadata/.log

У этих DCI поменялись ключи, сейчас там, например, Server.QueueSize.Max(DBWriter.Other). Эти изменения есть в новой версии темплейта, но автоматом мы не перезаписываем темплейты, чтоб не потерять изменения, которые мог cделать пользователь.

Что можно сделать:
а) Поменять конфигурационный параметр сервера ImportConfigurationOnStartup на Always, перезапустить сервер. Сервер при старте перезапишет темплейты.

б) Вручну импортировать новый темплейт, поставив галочку "Replace existing templates", через Tools->Import Configuration. Он лежит в C:\NetXMS\share\templates\netxms_server.xml

Yes, you can use createdBefore, createdAfter, updatedBefore, updatedAfter. Unix timestamp should be provided to these filters.

Also, you can filter by alarm state, e.g.
alarm=outstanding
or
alarm=outstanding,acknowledged

And there's a good thing resolveReferences=true, in this case you'll have names of all related objects in the json output.

There are also filters by user name, you can check in sources for these: src/client/nxapisrv/java/src/main/java/org/netxms/websvc/handlers/Alarms.java

Hi!

The way you tried is not yet implemented. What works is this way:

/alarms?objectId=123

/alarms?objectGuid=XXX

If you need to see alarms for all nodes under a container:
/alarms?objectId=123&includeChildObjects=true

Выложили

Should be available now

Memory leak has been fixed. It will be included in next release.

It should be possible to run without administrative rights. Communication of user support application happens through main agent process. So it's necessary to start agent process as well.
This could be done by some sort of bat file, so you can try packing all this into self extracting archive or something.
Current issue will be that agent process will produce a console window while it's running. It could be possible to add hiding of it's window is some of future releases.
You can try experimenting with all this - may be there will be some other issues on that way.

Created https://track.radensolutions.com/issue/NX-1945 for the memory leak.

Auto-refresh was implemented as a quick fix to get desktop video.
The proper way is, certainly, live video stream with some suitable codec, but this requires developer's time which is always busy with something.

Tags were reworked in 3.x - was added ability to have multiple tags for event. %u was deprecated. Currently you can use %[script_name] macro and make a script that will go through tags and return the value.
Created an issue https://track.radensolutions.com/issue/NX-1944 to make a macro that would return tags in concatenated form.