NetXMS Support Forum

Есть функция pow: https://wiki.netxms.org/wiki/NXSL:pow

You can use PING subagent and configure set of Icmp.Ping DCIs in the server, one for each host. You can use custom schedule to collect data once a day at 12:00, and configure threshold as necessary. Relevant part of the documentation: https://www.netxms.org/documentation/adminguide/icmp-ping.html

Best regards,
Victor

If V5U151 means Java 5 then it would not work for different reasons. Console requires at least Java 7.

Best regards,
Victor

На всякий случай - у вас субагенты не в той секции прописаны (хотя вроде как дублируются в правильной секции тоже).

Парсер выглядит правильным, должен был послать событие с кодом 200000 (кстати можно использовать имена событий вместо кодов). А событие было послано? Если нет, надо смотреть лог агента - можно в тэг парсер добавить опцию trace="9" и запустить агент с высоким дебагом - будет подробный лог парсера.

Можно добавить фильтрующий скрипт в правило, где отсылается сообщение. Из скрипта можно проверить статус других объектов и соответственно вернуть true или false дле выполнения правила или игнорирования.

Горячую клавишу назначить нельзя, а в контекстное меню добавляется через Configuration -> Object Tools.

Попробуйте отдельно поставить Visual C++ 2017 Runtime (https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads). Файл называется vc_redist.x64.exe или vc_redist.x86.exe.

А для какой платформы? Windows?

Hi,

it's a bug in a server. We will fix in in 2.2.5 release.

Best regards,
Victor

Hi,

in this debug output you see internal rule index, which is 0-based, so it's rule number 1. Node down was likely generated because agent was unresponsive and there are no other communication means for that node, so server consider it as down. There should be debug log records related to status poll of that node upper in the log.

Best regards,
Victor

Hi,

there are no standard procedure for that. You can though carefully insert necessary records into NetXMS DB from backup DB (while NetXMS server is stopped). What exactly for that device you need to restore?

Best regards,
Victor

Hi,

looks like a bug. What version you are using?

Best regards,
Victor

Hi!

Quote from: ages77 on March 28, 2018, 09:53:01 PM
The first is the utilization of the Subagent for monitoring the database (not NetXMS server db) but another instance deploy in another Host .I need to understand what i can configure and where (side agent into the host ) and side server into the nxmc .For example i need to know if the sqlServer instance rather then oracle instance is running and also the query for check the dimension of tablespace rather then simply query in user table.

What database exactly? There are sub-agents for monitoring Oracle, DB2, and MySQL databases. Also, you can use "dbquery" subagent to issue any query in database, so if you know how to extract data from system tables you can use that as well. For monitoring MS SQL Server you can use Windows Performance counters (accessible via "winperf" subagent).

Quote from: ages77 on March 28, 2018, 09:53:01 PM
The second is the Summary of alarm state . I need for example that every day at 12:00 PM an event send me (by email) the status of specific application server . This status is the situation of the system not necessary must in alarm state.

You can setup scheduled task that will run your script. Script can collect necessary data and generate an event that can be processed as usual and email can be generated from it.

Best regards,
Victor

Hi,

please check if netxmsd process is crashing. If yes, please provide a core dump or stack trace from core dump.

Best regards,
Victor

Hi,

I suppose it has something to do with selected database encoding, because it says that length of integer + varchar(255) key exceeds 767 bytes. As a workaround try to edit init script and reduce size of attr_name column in userdb_custom_attributes to 127 (you will not encounter any issues during server operation).

Best regards,
Victor