NetXMS Support Forum

3. There is filter script in map properties. It works in a way that this script is executed for each node that is about to be put on the map. If script returns true, node will be added to the map, if false, will not be added. Here's an example script:

rootNode = FindNodeObject($node, "your_root_node_name");
if (!rootNode) return false;

for (i : $node->children) {
  if (classof(i) == "Interface") {
    p = i->peerNode;
    if (p and p->id == rootNode->id) return true;
  }
}

return false;
This script finds your root node by name. Then for each node it's getting all interfaces, and check peer nodes for them. If your root node is peer node for one of the interfaces, script will return true.


1. and 2. seem to be not customizable, but I will check.

Since Debian uses systemd, After=   parameter in netxmsd.service should help.
https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Before=

Pls update, if you need an example

Agent communication DCIs are counters (similar as in SNMP), they are always increasing, that's fine. The interesting part is how fast it's increasing. As an option, you can add additional DCIs with enabled delta calculation.

Would be interesting to see graphs for these two Agent communication DCI for the same period as memory usage above.

This was just fixed, will be available in 4.3.1 when it will be released.

Most probable reason is that database engine gets stopped first. After that netxms waits for reconnection to the DB to write data prior to shutdown.

Странно все это.

Выглядит, как будто правило номер 3 вообще не сработало и не завело таймер. Можете на всякий случай показать еще то правило EPP которое для одной ноды на 2 минуты и правила номер 1 и 2.

You may try to run netxmsd under valgrind:

valgrind --leak-check=full --undef-value-errors=no --log-file=vg.log netxmsd -D1

Running it for a day will collect enough information, then when process is stopped, valgrind will collect log file with information about memory leaks.
The problem is that valgrind requires much more RAM then netxmsd itself, as it keeps information about every allocated piece of memory, so chances are that it won't start at all.


The other option is to compile netxms from sources, adding --enable-sanitizer to ./configure command. This would print information about memory leaks to the console and consumes a bit less memory then valgrind approach.


Also can you give a list of things that you use in your monitoring - agent tunnels, snmp, agent monitoring, actions that execute commands on management server, notification channels - any functionality that is not configured out of the box.

What version of Ubuntu are you using?

Это парные события, SYS_AGENT_OK должен быть только после SYS_AGENT_UNREACHEABLE. Можно проверить в Event Log по конкретной ноде, какие событие происходили.

У вас во втором правиле на 1 ноду больше, возможно дело в этом. В Event Processing Policy в качестве source object можно указывать не только отдельные ноды, но и контейнеры. Можно сделать специальный контейнер этих целей и даже автоматизировать добавление нод в него с помощью autobind script.

Was unable to replicate this.
Is this background image configured as rack Passive Element? Can you show properties of that passive elements?
Do you also have some other nodes that are present in this rack? Do they use default images or custom? Can you also show screenshots of their rack properties?

Windows agent nstaller on netxms.org/downloads has been updated, please try it

Pollers ans Datacoll look ok, also it's worth to check the wait time for them.
Syncer is good.

Main is not good - it has average wait time of 59 seconds. Main thread is doing a lot of different things - executes commands on management server, communicates with proxies, calculates business service related stuff...

What are values of
ThreadPool.Main.MaxSize
ThreadPool.Main.BaseSize
?

А можно и мне эти логи, здесь в личном сообщении

В Event Processing Policy есть правило которое реагирует на SYS_INCORRECT_NETMASK. Можно в нем добавить исключение на конкретную ноду.

Про ICMP в доке достаточно подробно описано, но спрашивайте если там что-то не понятно
https://www.netxms.org/documentation/adminguide/icmp-ping.html

Hi!

What exactly version of netxms are you running?
Can you show output of "sh st" from Tools -> Server Console?


Are default System -> NetXMS server templates up to date? They are not imported automatically - you can set server configuration parameter Server.ImportConfigurationOnStartup to "Always" and restart the server.

From the server template it would be worth to see graph for DCI "NetXMS server: physical memory used by process" (together with "System: available physical memory").
And graph for "Server QueueSize DBWriter.Total: Current" - that's how much data is waiting to be written to the DB. If DB is slow, this might grow and consume memory.


What about DB, is it running on the same VM?
Anything else running on this VM? NetXMS Web UI?