NetXMS Support Forum

Nested custom attributes are not supported. But you can get all the data you need within the script, either by using object attributes, e.g.

$node->ipAddr

or by calling expandString method of NetObj, Event or Alarm , e.g.:

$node->expandString("%n")

Configuration polls are executed periodically on their own schedule (previously it was so that configuration poll was executed only if status poll detected node up situation, but that had issued - e.g. SNMP community string changed and that required conf poll to find the correct one).

For tunnel nodes, however, conf poll should be scheduled right after tunnel is established, so you can try that.

There is no way to force a poll from NXSL, I've created an issue so at some moment of time this could be added: https://track.radensolutions.com/issue/NX-2480

A bit crazy approach which might currently work - we have an option to redefine poll intervals using custom attributes, e.g:
SysConfig:Objects.ConfigurationPollingIntervalso status poll hook can detect that node comes up and set such custom interval (with value say 60) and conf poll hook would delete this custom attribute.

Is it legacy or the new web UI. On what OS Firefox is running?

First advice would be to try latest version of nxmc, for 4.3. it's 4.3.7
https://netxms.org/download/releases/4.3/

Здравствуйте,


Какое-то краткое описание есть тут, возможно оно устарело
https://www.netxms.org/documentation/adminguide/quickstart.html

логика процесса такая:
event (событие) -> action (действие) -> notification channel


при переходе в node down (а также при срабатывании трешхолда и много чем еще) происходит событие. Дальше есть Event processing policy (EPP) - набор правил где решается, что по каждому событию делать.

в правиле EPP может вызываться действие

действия конфигурируются в Configuration->Actions. Нас интересует тип Send notification. Тут нужно выбрать конкретный notification channel.

это настраивается в configuration -> notification channels. Нас интересует драйвер SNMP. В Driver Configuration пишутся параметры для дравйвера в виде
параметр=значение
описание параметров тут: https://www.netxms.org/documentation/adminguide/event-processing.html#drivers


Когда notification channel сохранен, по правой кнопке мыши по нему (в новом клиенте, не legacy) будет пункт send notification - так можно проверить что что-то шлется

И в 4.4.3 добавили несколько макросов:
-  New event processing macros %d (DCI description), %D (DCI comments), %L (object alias), and %C (object comments)

The option to get older release on Debian is to compile from sources, but this might be a bit complicated.

What about the first option - can you upgrade your current installation of netxms and migrate the database then?

Yes, we need same version of NetXMS to migrate db.
To summarize the possible ways:

- upgrade the "old" netxms first, then export the database and import into same version.

- install older NetXMS on the new system - for Debian/Ubuntu repository actually stores a number of previous versions, you can check with:
apt-cache policy netxms-server

Then you can install specific version, but you need to specify the version also for all netxms packages which server depends upon. E.g. for to install agent there's two more packages, for server there are a bit more:
apt install netxms-base=4.3.4-1 netxms-dbdrv-sqlite3=4.3.4-1 netxms-agent=4.3.4-1

- export file produced by nxdbmgr is actually sqlite database. So you can specify that file in netxmsd.conf:
DBDriver=sqlite.ddr
DBName=/path/to/your/file/netxms.db
and start the server. It will upgrade the sql file to the latest version, then you can stop the server and use nxdbmgr to perform import.

The logic is that if "Samples" is set to 3, then all last three collected values should be "1" to trigger the threshold. If just one non "1" value comes, this means "last 3 values should be equal to 1" becomes false and it instantly generates threshold recovery event.

You can use script threshold, there you can use https://www.netxms.org/documentation/nxsl-latest/#func-getdcivalues function to get a number of last values and make the decision in the script. Drop a line if you need an example for such script.

This view was just forgotten to move to the new UI, thanks for reminding.

Central server is typically can handle thousands of nodes on it's own, so there's no much need in offloading it, but yes, proxies can be used that way. More interestingly - with cache mode on proxy can collect data even if there's no connection to central server. You can have several proxies on a zone - in this case they will be in HA mode, exchange hearthbeat messages and data collection will move to one if another one goes down

nxmc-light is the name of visual theme. In the legacy UI we had a few of these, in the new one there's only one so far.

First thing needed is Java 17

Port 161 is probably not needed - is there anything inside the container that listens to it? Anyways, if there is - agent should be able to work as a proxy for the node where it is running.

For proxying - you need to have:
EnableProxy=yes
EnableSNMPProxy=yes
SubAgent=ping
SubAgent=ssh            # optional, only if you want to use ssh monitoring
in configuration of the agent

Is agent able to send ICMP requests - you can try collecting Icmp.Ping(1.2.3.4) metric from that agent

You can also try operation without network discovery - by adding a node for a device in that zone and manually specifying that proxy in properties of the node.

Yes, correct, since devices in your management network are directly accessible from NetXMS server, there is no need for zoning to monitor them.