NetXMS Support Forum

What you mean by "monitor DCI"? DCI has a value by itself, you don't need another DCI to monitor it. I think you was asking about network service objects...

Best regards,
Victor

Макрос %a. Все возможные макросы описаны здесь: https://www.netxms.org/documentation/netxms_user_manual.pdf в разделе 8.6.

You can use ChildStatus(*) internal parameter to monitor status of child objects for a node (interfaces and services). It takes child object ID or name as an argument, like


ChildStatus(eth0)


for interface eth0 on the node.

Best regards,
Victor

Hello!

It is possible already. File.Count has the following arguments:

File.Count(root_path, [pattern], [recursive])

You can define pattern as usual with * and ? characters, and if you wish to scan directories recursively, you should pass 1 as recursive arguments.

For your example

x:\folderA\subfolder\a\file1.txt
x:\folderA\subfolder\b\file2.txt
x:\folderA\subfolder\c\file3.txt
x:\folderA\subfolder\c\file4.txt

File.Count(x:\FolderA, *, 1) will return 4
File.Count(x:\FolderA, file2.*, 1) will return 1
File.Count(x:\FolderA, *) will return 0

Best regards,
Victor

Начиная с версии 0.2.21 это можно делать - в скрипте выставляем переменную CUSTOM_MESSAGE в нужное значение, и потом можем получить его используя макрос %M при создании аларма или actions.

Крестики вместо иконок появляются вместе с Internet Explorer 7 Вообще Alarm Viewer скоро будет новый.
Чтобы проговаривались тексты на русском, должен быть русский text-to-speech (TTS) engine. Вот здесь вроде что-то есть: http://www.bytecool.com/voices.htm. Но сам я никогда не пробовал ставить дополнительные языки в TTS.

All System.CPU.Usage parameters works with logical processors - i.e. single physical processor with hyper threading will be seen as two logical processors, quad-core processor will be seen as 4 logical processors, and dual-core processor with hyper threading will be seen as 4 logical processors.

System.CPU.Usage gives you an average utilization for all processors. System.CPU.Usage(*) accepts zero-based logical CPU number as an argument. For system with 4 logical processors you will be able to use ids 0, 1, 2, and 3.

That was about CPU utilization. If we come to CPU load, there are no parameters for per-processor load, because system has only one process run queue, and usually processes can be dispatched for execution to any free CPU.

Hope this helps!

Best regards,
Victor

It' because DCI data type is unsigned int64, and automatic conversion from it to float (real) is not allowed. If you take a look at event log, you most likely will see a lot of SYS_SCRIPT_ERROR events. You have two options: change DCI data type to "float" or "integer", or do an explicit type conversion like this:


int64($1) / GetDCIValue($node, FindDCIByName($node, "System.Memory.Physical.Total")) * 100


Currently NetXMS will leave original value if transformation script fails - not a correct behaviour probably.

Best regards,
Victor

Пока нельзя. Единственный вариант - это отключить configuration polling на роутере и удалить подсети, но это плохой workaround.

Some additional info can be found in this thread: https://www.netxms.org/forum/index.php/topic,289.0.html.

Assuming that you have DCI for parameter System.Memory.Physical.Total, your transformation script may look like this:


sub main()
{
   total = GetDCIValue($node, FindDCIByName($node, "System.Memory.Physical.Total"));
   return $1 / total * 100;
}


or simplified to


$1 / GetDCIValue($node, FindDCIByName($node, "System.Memory.Physical.Total")) * 100


Best regards,
Victor

Поменять нельзя. Но могу это сделать в следующем релизе, технически это не сложно.

Должно быть


sub main()
{
   return ($2 == 4227794) ? 1 : 0;
}


Just to make sure that we are understanding each other correctly: processor load and processor utilization are different parameters - processor utilization, or usage (represented by System.CPU.Usage) is a percentage of time spent by processor outside idle loop, and processor load (represented by System.CPU.LoadAvg) is an average length of process run queue (or average number of processes ready to run but waiting for execution because CPU is busy running other process). So, when CPU utilization goes to 100%, CPU load can be 2 - it just mean that in average, 2 processes are waiting for execution - which is normal.
CPU utilization is mostly used in Windows world, and CPU load average - in UNIX world. We support both of them on all platforms.

Best regards,
Victor

I'm working on it.

Best regards,
Victor

Not in the near future, because our time mostly goes to more important core features and Linux console. I can provide help if somebody will write that, but I will not be able to do it myself - only because of lack of time.

Best regards,
Victor