NetXMS Support Forum

V etom sluchae pridetsja delat' dva pravila s filter-scriptami. Obschaja posledovatel'nost' shagov:

1. V nastrojkah trapov vitaskivaem varbind .1.2.3.4.5 v parameter eventa (pust' budet parametr nomer 2)
2. V event policy delaem pravilo dlja generacii alarma: event, naznachennij trapu, i filtering script


$2 == 1


kljuch mozno sdelat' na osnove kakogo-nibud' teksta i _%i - chtobi razlichat' alarmi s raznih hostov.

3. V event processing policy delaem vtoroe pravilo - dlja terminate alarma. Event i kljuch alarma ukazivaem te-ze, a filtering script delaem kak


$2 == 0


teper' pervoe pravilo budet srabativat', esli nash varbind raven 1, a vtoroe - esli on raven 0.

It's a bug in MIB compiler - in lines 18622 and 18624 there are tab between words OBJECT and IDENTIFIER instead of space. As workaround, replace these tabs with space character and MIB should compile without error.

Best regards,
Victor

Quote from: Ethril on May 18, 2009, 06:03:53 PM
P.S. И ещё вопросик вдогонку: не планируется ли доработать в будущем модуль для update/deploy клиентов, чтобы заодно распространять на них файлики с парсерами? Чтобы не копировать ручками .xml-файлик на 20 серверов.

Планируется - будет возможность централизованно распространять конфиги, скрипты, и т.д.

Quote from: Ethril on May 18, 2009, 06:03:53 PM
Расскажите, плиз, подробнее про <event param="1"> в парсере.
Для начала хочу передавать в NetXMS текст эвента ошибки из виндового System Log.
Сделал простейший парсер:

Code Select Expand


<parser>
<file>*System</file>
<rules>
<rule>
<level>1</level>
<match>*</match>
<event params="1">100012</event>
</rule>
</rules>
</parser>

Теперь при появлении ошибки в System Log, в NetXMS Event Browser'е появляется эвент, но без текста ошибки, хотя Message Template у него стоит %1. Что-то недокрутил?

Ту часть текста, которую надо передать как параметр события, надо брать в скобки, например:

(.*) - весь текст будет взят как параметр
^Error (.*) - текст после слова Error будет взят как параметр

Поскольку события привязаны к тому компьютеру, который делает ping, то и %i всегда один и тот-же. Если PING_DELAYED генерируется как результат срабатывания порогового значения, то можно использовать PING_DELAYED_%i_%5 - вместо %5 будет подставлен идентификатор DCI, что даст разные ключи для разных параметров.

Скорее всего. А какое окно восстанавливается, а какое нет?

Discussed here: https://www.netxms.org/forum/index.php/topic,615.0.html

Hello!

No, it's not possible (without C programming). I'll add this to feature requests.
Currently, you can start actions when new node added to the system (by handling SYS_NODE_ADDED event), but to change node attributes from action, you have to write your own C (or Java) program which will access NetXMS server via client API.
I'll add appropriate functions to NXSL so you will be able update object attributes from internal scripts.

Best regards,
Victor

Sintaksis vigljadit pravil'nim. A v loge agenta est' chto-nibud'?

A versija konsoli s versiej servera sovpadaet? poskol'ku na drugih kompah vse v porjadke, to problema ili v samoj konsoli, ili v nesovmestimosti versij. Esche prishlite esli mozno 2 screenshota - tam gde vse horosho, i tam gde problemi.

Hello!

You should use == for compare operation. = is an assignment operation.

For example:


a = 1


means "assign value 1 to variable a"

and


a == 1


means "test if variable's value is 1".

Second error is that $node variable is an object, and you need to compare it's name attribute. To access it, use


$node->name


And compare always returns 1 or 0, so you can omit ? 1 : 0 part and simply use


left($node->name,6) == "FG100A"


So, correct script will looks like


sub main()
{
   return left($node->name, 6) == "FG100A";
}



Best regards,
Victor

Hi all!

I think that we can consider this project as abandoned.

As for better network maps, we are now actively working on completely new management console, which is based on Eclipse platform and written in Java. It will have network map plugin, which should be better. And, if someone has experience in Java/Eclipse development, you are welcome to develop plugins for this new console.

Best regards,
Victor

It's not very difficult - mostly UI change. Also, for escalation you can simply replace alarms (but this depends on how you create your alarm keys). Alarm key is also used by server to identify duplicate alarms, so if you generate new alarm with same key as existing one, server will update all fields in existing alarm except creation time, and increase repeat count.

Best regards,
Victor

Zavel issue v bugtracker chtobi ne zabit' ispravit'. Spasibo

https://www.netxms.org/bugtrack/view.php?id=254

Quote from: jdl on May 11, 2009, 06:12:41 PM
By the way, is there no way to define "terminate alarm" while keeping the message in the event list?
So having access to both "terminate alarms" and "Generate new alarm" sections?

I'm not sure I understand correctly - you wish to terminate alarm and then generate new alarm immediately? Then you have to define two rules with identical matching part, first will terminate alarm, and second create new alarm.

Best regards,
Victor