NetXMS Support Forum

В выделенном правиле должно быть DC_%i_%3. Можно ли прислать следующую инфу:
1. скриншот конфигурации аларма для правила 1;
2. скриншот конфигурации threshold для DCI (список threshold'oв и настройки конкретного threshold'a).

И в самом деле удивительно  Буду думать...

Реализована, так что похоже на баг. Возможно агент по каким-то причинам не понимает ответа на HELLO. А можно ли прислать лог сессии?

Hello!

"Calculate status as" determines how object's status should be calculated based on child objects statuses. For objects without child objects (like conditions) it has no meaning.
"Propagate status as" determines how object present it's status to parent object(s). For example, you have a switch with various interfaces. Normally, when interface goes down, it's status changes to CRITICAL, and status of entire node object changes to CRITICAL (and so on up to the root). However, if you have not very important interfaces and wish that node status changes not to CRITICAL, but to WARNING when this interface  goes down, you can change "Propagate status as" property of interface object so it will propagate it's CRITICAL status as WARNING.

Best regards,
Victor

Пока никак, он просто делает connect. В  будущем планируем начать использовать.

Добрый день!

SMTP:
request = адрес для отсылки мейла, response не используется.

SSH:
оба поля игнорируются, проводится ssh handshake без логина.

POP3:
request = user:password, response не используется.

FTP пока не реализован.

Скорее всего остается активным какой-то аларм со статусом CRITICAL (статус ноды складывается из статусов интерфейсов и алармов). Если этому аларму сделать terminate, то статус ноды должен изменится на NORMAL.

Релиз будет в августе, постараюсь учесть как можно больше пожеланий. В последнее время в связи со всяческими рабочими и домашними проблемами работа над проектом замедлилась, но я надеюсь что скоро ситуация изменится.

Quote from: cme on August 17, 2007, 01:47:55 AM
Second question:

I have the event SYS_THRESHOLD_REACHED let's say for this CPU monitoring...
If I further want to watch the DiskUsage.. (if it's above 90%)
Do I have to create another new event like this or use another one?
So do I have to create such a event for every "thing" that is watched?
Example:
CPU -> CPU_TOO_HIGH -> action: email "CPU of PC123 too high.."
Disk -> DISK_FULL -> action: "Disk of PC123 too full.."
..

Yes, it's the main idea - you create different events for different thresholds, so you can process them differently. After NetXMS installation you already have some example events for threshold violations - their names starts with DC_ prefix.

Also, you may create different events for different thresholds (for example HIGH_CPU_USAGE and LOW_DISK_SPACE), but handle them identically - for example, write one rule in event processing policy:

add both HIGH_CPU_USAGE and LOW_DISK_SPACE to event field;
in alarm generation field as alarm text use %m macro, which will expand to actual event's text.

With this approach, you can have relatively simple event processing policy but use meaningful texts in alarms and messages.

Quote from: cme on August 17, 2007, 01:47:55 AM

One task of NetXMS will be to inform the admin about any (already added in NetXMS) PC of the net which has a
CPU usage of more than 80%.
I already know that I can add the usage in "data collection" --> then add a rule in event processing policy editor with
action "SYS_THRESHOLD_REACHED" that send an static text via email to the admin.

Now do I have to do these steps for every host?

I want to do that dynamically that in the mail the hostname will be shown like
"CPU of PC23 is above 80%..."

Hello!

You can achieve this using templates:
1. Create template object (in Templates subtree)
2. In data collection configuration for template object, create DCI for CPU utilization as usual
3. Apply template to nodes where you wish to check CPU utilization

In event processing policy, you can use macros in alarm texts. For example, if you wish to include node name and actual CPU utilization in alarm (or e-mail text, etc.), you may write your text like this:
CPU utilization on node %n is %4%%

%n will be replaced by node name, %4 by actual DCI value, and %% with single % character. You can find complete list of available macros in User's Manual (section 8.6) or here:
https://www.netxms.org/documentation/macros.shtml

Best regards,
Victor

Очередной баг Должен был быть параметр --with-oracle, но я забыл его добавить. Исправлю в 0.2.19.

Теперь понял  У каждого threshold'a есть два события - одно генерируется когда threshold активируется (условие выполняется), второе - когда деактивируется (условие больше не выполняется). Соответственно в качестве реакции на первый event делаем аларм с неким ключом, а на второй - terminate alarm по тому-же ключу. Я обычно поступаю следующим образом: в качестве activate event'ов на разные threshold'ы использую разные event'ы но когда делаю из них алармы то использую одинаковый шаблон для ключа: DC_%i_%5; как deactivation event использую всегда только стандартный SYS_THRESHOLD_REARMED, и в качестве реакции делаю terminate alarm по ключу DC_%i_%3. Таким образом, при нарушении порогового значения аларм создается, а при возврате к нормальному уровню - удаляется.

Если мы используем первый вариант, то трешолдов не должно быть. В поле Alarm для события SYS_IF_UP ставим "terminate alarm" и ключ из правила для SYS_IF_DISABLED.

Так как они видны в Network -> Properties, например Local Area Connection.

Quote from: jdlds on August 10, 2007, 04:44:06 AM

Another issue i've encountered is using the PDH.countervalue for data collection.  This seems to work fine for some counters but not others.

I tried: '\Memory\Committed Bytes' and this seems to work just fine
but when i tried
'\PhysicalDisk(_Total)\Disk Write Bytes/sec' this always returns 0.

if anyone can shed some light on this, that would great.

Some counters (like physical disk counter you mention or CPU utilization counters) requires at least two samples to be taken to calculate value. Such counters should be polled in background by agent. To configure agent to do so, use Counter parameter in WinPerf section, like below:

*WinPerf
Counter = DiskWriteBytes:"\PhysicalDisk(_Total)\Disk Write Bytes/sec":60:A:INT:Average number of bytes per second written to disk for last minute

There are several fields separated by colons (. First is the name for new parameter (DiskWriteBytes in our example); second is counter path; third is number of samples to calculate average value - minimum is 2, and in our example it's 60 (because we need average value for last minute); fourth field is a collection class - it can be either A (collect values every second), B (collect values every 5 seconds), or C (collect values every 30 seconds); fifth field is a data type - it's only a hint for "select parameter" dialog in console and is not used by agent; and sixth field is a parameter description which will be shown in parameter selection dialog.

After you define your new counter, you can access new parameter on agent by using name specified in the first field.

Best regards,
Victor