NetXMS Support Forum

Крестики вместо иконок появляются вместе с 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

It's still there unfortunatelly... We have half-done code for event log monitoring, which was frozen some times ago due to lack of free time.

Best regards,
Victor

Hello!

Looks correct. Do you have any problems with it? Also, since version 0.2.20 you can collect total amount of RAM as separate DCI and use it's value in calculation instead of hardcoded value.

Best regards,
Victor

Is there any messages in agent's log (or system event log) when agent starts?

Best regards,
Victor

Hello!

Both are not possible now, but already put in wishlist by many people.

Best regards,
Victor

Hello!

Looks like a bug in MIB compiler. As a workaround, just comment out or delete entire DEFVAL line - it is not used by compiler anyway.

Best regards,
Victor