NetXMS Support Forum

Hello all!

Vesrion 0.2.28 is out. Changes from previous release:

- Added encryption support for SNMP version 3
- Fixed compatibility issues with NetXMS SNMP version 3 implementation and Cisco devices
- Automatic network discovery improved
- LOGSCAN subagent removed (superseded by LOGWATCH subagent)
- Fixed issues: #234, #259, #260, #261, #262, #263, #264

Best regards,
Victor

Hello all!

NetXMS version 0.2.27 is released.

Changes from previous release:

- Added support for SNMP version 3 (without encryption)
- Log monitoring improved
- Built-in scripting language (NXSL) improved
- Various minor improvements
- Fixed issues: #223, #249, #250, #252, #253, #254, #255, #256, #258

Best regards,
Victor

Hi all!

Nearly six years ago I started NetXMS as my hobby open-source project. Then I found that quite a few people actualy use it and like it. This gave me a good reason not to stop. Few other guys have joined me and we continued development with increased efforts and passion - because we knew we do something really cool. Few years later I found myself having two fulltime jobs - my day job, and NetXMS. Couple months ago I realized that one of the jobs must go, so now NetXMS is my day job. I've set up a company - Raden Solutions - which is supposed (among few other things) to handle NetXMS commercial support and training activities. I hope that this will allow me to spent more time and resources on NetXMS development, resulting in better product with faster development cycle. And if by any chance you need "official" NetXMS support or training - you know where to look  

Company web site: http://www.radensolutions.com

Best regards,
Victor

Hi all!

Attached is updated logwatch subagent (for 32 bit Windows). All outstanding issues with Windows event log monitoring should be fixed - it should work with Security log and custom application logs, and Windows 2008 related problems should be fixed as well. I'll be very appreciated if someone test it on different platforms and logs. You can simply replace old logwatch.nsm in 0.2.26 agent with attached one.

Best regards,
Victor

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

What operating system you are using for NetXMS server?

If you are using unlisted operating system, please comment what, if possible.

How many nodes you are monitoring with NetXMS?

What database you are using as backend?

Hello all!

NetXMS version 0.2.23 is released.

Changes from previous release:

- Implemented event forwarding between NetXMS servers
- Added new subagent LOGWATCH for log monitoring
- Implemented syslog message monitoring on built-in syslog server
- New agent configuration parameter: WaitForProcess
- Number of consecutive polls can be specified for "last value" threshold
- Implemented "Clear DCI data" function
- Management packs improved
- Usage of ifXTable for interface naming made configurable
- NXSL: added new attribute "status" for node objects
- Implemented resending of failed e-mails
- Database checking procedure improved
- Windows console:
   - Added support for negative values on graphs
   - Implemented editing of predefned graphs
   - Implemented cut/copy/paste in event policy editor
- Java API introduced
- Fixed issues: #31, #74, #146, #218, #228, #235, #236, #237, #238

Best regards,
Victor

Hi all!

I have moved all topics related to compilation of NetXMS for Windows platform to the development board, because compilation is not a part of normal installation process on Windows. From now on, please post all such topics into appropriate development board.

Best regards,
Victor

Выложил версию 0.2.23-rc3 в https://www.netxms.org/download/rc для желающих потестировать мониторинг логов.
Добавлена возможность:
1. проверять сообщения, принимаемые встроенным syslog сервером на соответствия шаблонам и создавать события при соответствии;
2. через агента проверять записи в текстовых логах на соответствия шаблонам и создавать события при соответствии;
3. на Windows - то-же самое для Windows Event Log.

Для 1. надо обновить сервер, для 2 и 3 достаточно поставить новых агентов.

Как настраивать монтторинг логов через агента:

1. Создать необходимые события (через Control Panel -> Events);
2. В конфиге агента добавить загрузку субагента logwatch.nsm (libnsm_logwatch.so на UNIX);
3. Для каждого лога добавить запись вида Parser = config_file в секции LogWatch. Например так:


*LogWatch
Parser = /opt/netxms/etc/log_1.xml
Parser = /opt/netxms/etc/log_2.xml


4. Создать конфиги парсеров. Каждый конфиг - это отдельный XML файл следующего формата:

<parser>
   <file>file_name</file>
   <rules>
      <rule>
         <match>regexp</match>
         <event params="n">event_code</event>
      </rule>
      ...
   </rules>
</parser>

Таг <rule> можно повторять сколько необходимо. Аттрибут params в таге event указывает, сколько подстрок (обозначенных в regexp'e скобками) надо передать как параметры события (их потом можно использовать через макросы %1, %2, ...). Если параметров нет, то фттрибут events можно не указывать.
Для мониторинга Windows event logs вместо имени файла надо указывать *log_name, например *System

Примеры:

1. Послать событие с кодом 1000 если в строке лога найдено слово "error":
<rule>
   <match>error</match>
   <event>1000</event>
</rule>

2. Послать событие с кодом 2000 если строка начинается со слова "warning:", при этом текст после "warning:" передать как параметр:

<rule>
   <match>^warning: (.*)</match>
   <event params="1">2000</event>
</rule>

Hello all!

NetXMS version 0.2.22 is released.

Changes from previous release:

- Scripts now can be used to form event's message (via %[..] macro)
- Scripts in event processing policy now has access to node properties
  via $node variable and to event properties via $event variable
- Implemented XML encoding for NXCP messages
- Added support of custom object attributes
- Minor map improvements
- Fixed issues: #196, #201, #216, #220, #221, #222, #225, #226, #230, #231

Best regards,
Victor

Reshil perenesti kommentarii k opisannoj probleme v forum, tak udobnee budet. Original'nij report:

Не могу точно сказать где, но выглядит это примерно так же как и ошибка несоответствия %s и %S. Проявляется не регулярно и на разных нодах.

1. Ошибка в теле письма (макросы)

Описание: в случае, если в шаблонах почтовых извещений используется конструкция типа ...

поле "E-mail Subject":
%S (%t): параметр "%2" на сервере %n

поле "Message text":
ВРЕМЯ ВОЗНИКНОВЕНИЯ:\t%t\nМЕСТО ВОЗНИКНОВЕНИЯ:\t%n[%a]\nИСТОЧНИК СОБЫТИЯ:\t%2\nСТАТУС СОБЫТИЯ:\t\t%S\n\n%m

и в обрабатываемом Event'е (Message template) используется конструкция:
Внимание! Превышено допустимое значение параметра "%2"! Текущее значение: +%4C (допустимо: +%3C)

... то в основном приходит правильная почта (ну.. почти нормальная, так как Severity %s не равно %S):

Subject:
Minor (14-Jul-2008 17:09:18): параметр "[DL] [MB Ambient Temp] Температура Системы" на сервере test.server.ru

Body:
ВРЕМЯ ВОЗНИКНОВЕНИЯ: 14-Jul-2008 17:09:18
МЕСТО ВОЗНИКНОВЕНИЯ: test.server.ru[10.100.144.33]
ИСТОЧНИК СОБЫТИЯ: [DL] [MB Ambient Temp] Температура Системы
СТАТУС СОБЫТИЯ: Minor

ОПИСАНИЕ СОБЫТИЯ: Внимание! Превышено допустимое значение параметра "[DL] [MB Ambient Temp] Температура Системы"! Текущее значение: +40C (допустимо: +40C)

* * *

Но вот иногда где-то что-то заедает и вместо нормального ответа я получаю такой:

Subject:
нормальный, как в предыдущем примере

а вот текст...

Body:
ВРЕМЯ ВОЗНИКНОВЕНИЯ: 14-Jul-2008 17:09:16
МЕСТО ВОЗНИКНОВЕНИЯ: test2.server.ru[10.10.34.53]
ИСТОЧНИК СОБЫТИЯ: [DL] [MB Ambient temp] Температура Системы
СТАТУС СОБЫТИЯ: Minor

ОПИСАНИЕ СОБЫТИЯ: Внимание! Превышено допустимое значение параметра "[DL] [MB Ambient Temp] Температура Системы"! Текущее значение: +C (допустимо: +0x000005A7C)

2. Ошибка в заголовке и теле письма
Описание: не все макросы заполняются данными, и поэтому нарушается подстановка

Шаблон почтового извещения полностью аналогичен предыдущему.

Используемый Event (Message template): Агент NetXMS не отвечает

получаю сообщение:

Subject: Minor (11-Jul-2008 20:01:06): параметр "" на сервере test3.server.ru

ВРЕМЯ ВОЗНИКНОВЕНИЯ: 11-Jul-2008 20:01:06
МЕСТО ВОЗНИКНОВЕНИЯ: test3.server.ru[10.100.143.162]
ИСТОЧНИК СОБЫТИЯ:
СТАТУС СОБЫТИЯ: Minor

Агент NetXMS не отвечает

Нельзя ли хоть чем-нибудь заполнять Event Source? Или это ошибка?

--------------

v otvetah sejchas prokommentiruju.

Problem on FreeBSD 6.2:

Making all in core
gmake[4]: Entering directory `/usr/home/sysadmin/netxms-0.2.22-rc1/src/server/core'
/bin/sh ../../../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../include -I../../../src/server/include  -I/usr/local/mysql/include -I/usr/include/mysql -I/usr/mysql/include -I/usr/local/include/mysql -I/usr/local/mysql/include/mysql -I/usr/mysql/include/mysql -I/usr/local/include -D_THREAD_SAFE -D_THREAD_SAFE -DPREFIX=\"/usr/local\" -DPREFIXW=L\"/usr/local\" -DDATADIR=\"/usr/local/share/netxms\" -DLIBDIR=\"/usr/local/lib\"  -g -O2 -fno-rtti -fno-exceptions -fno-const-strings -Wno-deprecated -MT nxsl_classes.lo -MD -MP -MF .deps/nxsl_classes.Tpo -c -o nxsl_classes.lo nxsl_classes.cpp
g++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../include -I../../../src/server/include -I/usr/local/mysql/include -I/usr/include/mysql -I/usr/mysql/include -I/usr/local/include/mysql -I/usr/local/mysql/include/mysql -I/usr/mysql/include/mysql -I/usr/local/include -D_THREAD_SAFE -D_THREAD_SAFE -DPREFIX=\"/usr/local\" -DPREFIXW=L\"/usr/local\" -DDATADIR=\"/usr/local/share/netxms\" -DLIBDIR=\"/usr/local/lib\" -g -O2 -fno-rtti -fno-exceptions -fno-const-strings -Wno-deprecated -MT nxsl_classes.lo -MD -MP -MF .deps/nxsl_classes.Tpo -c nxsl_classes.cpp  -fPIC -DPIC -o .libs/nxsl_classes.o
nxsl_classes.cpp: In member function `virtual NXSL_Value* NXSL_EventClass::GetAttr(NXSL_Object*, char*)':
nxsl_classes.cpp:135: error: call of overloaded `NXSL_Value(time_t)' is ambiguous
../../../include/nxsl_classes.h:159: note: candidates are: NXSL_Value::NXSL_Value(const NXSL_Value&)
../../../include/nxsl_classes.h:196: note:                 NXSL_Value::NXSL_Value(const char*) <near match>
../../../include/nxsl_classes.h:195: note:                 NXSL_Value::NXSL_Value(double)
../../../include/nxsl_classes.h:194: note:                 NXSL_Value::NXSL_Value(QWORD)
../../../include/nxsl_classes.h:193: note:                 NXSL_Value::NXSL_Value(DWORD)
../../../include/nxsl_classes.h:192: note:                 NXSL_Value::NXSL_Value(INT64)
../../../include/nxsl_classes.h:191: note:                 NXSL_Value::NXSL_Value(LONG)
../../../include/nxsl_classes.h:190: note:                 NXSL_Value::NXSL_Value(NXSL_Array*) <near match>
../../../include/nxsl_classes.h:189: note:                 NXSL_Value::NXSL_Value(NXSL_Object*) <near match>
../../../include/nxsl_classes.h:188: note:                 NXSL_Value::NXSL_Value(const NXSL_Value*) <near match>
gmake[4]: *** [nxsl_classes.lo] Error 1
gmake[4]: Leaving directory `/usr/home/sysadmin/netxms-0.2.22-rc1/src/server/core'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory `/usr/home/sysadmin/netxms-0.2.22-rc1/src/server'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/usr/home/sysadmin/netxms-0.2.22-rc1/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/home/sysadmin/netxms-0.2.22-rc1'
gmake: *** [all] Error 2

This topic has been moved to Идеи и предложения по функциональности NetXMS.

https://www.netxms.org/forum/index.php?topic=383.0

Vopros k tem kto ispol'zuet russkij Windows - kak vedet sebja agent? Est' li kakie-to specificheskie problemi? Osobenno interesujet winperf subagent - vozvraschaet li on parametri System.Uptime, System.ThreadCount, System.CPU.LoadAvg i System.CPU.Usage?

Best regards,
Victor

Hello all!

NetXMS version 0.2.21 released. Changes from previous release:

- Multiple network maps implemented
- Added parameter ListenAddress to all services (server, web server, agent)
- New possible value for UseInterfaceAliases - concatenate name with alias
- Added possibility to create custom message in event matching script and
  use it in alarms and actions
- WMI subagent added
- SNMP sysDescr and agent's uname now polled and displayed
- New features in Windows console:
   - Possibility to use non-local timezone in Windows console
   - Default graph settings can be changed
- AIX subagent: implemented System.CPU.LoadAvg* and System.Uptime parameters
- Fixed issues: #193, #194, #198, #204, #209, #211, #212, #213, #214, #215

Best regards,
Victor

From messages:

Quote from: Rando on April 11, 2008, 02:47:38 AM
Sorry, I didn't read the last part of the message.  Yes, you can transfer this to the forum.  I'm still struggling with the scripting.  Is there any examples with descriptions I can look at to see the structure and usage?  I'm just going through the manual right now.

Quote from: Victor Kirhenshtein on April 07, 2008, 04:37:10 PM

Quote from: Rando on April 07, 2008, 09:19:18 AM
I'm still learning the NetXMS software and have a wireless base station and remote wireless radios which is SNMP capable and I do get a signal value and a noise value.  For me to calculate the signal to noise ratio I have to subtract these two numbers to create a 3rd value that I would need to track.  Is there any way NetXMS can do this?

Yes, it's possible. You should define two DCIs, one will collect signal value, and other noise value. Then, for one DCI you can create transformation script, which will access last value of other DCI and use it in transformation. You can access other DCI value using built-in functions GetDCIValue and FindDCIByName or FindDCIByDescription. See user's manual for description of these functions (section 8.5.3).
You script may looks like following (assuming that you are transforming signal value and your noise DCI called "Noise Level"):

Code Select Expand


$1 - GetDCIValue($node, FindDCIByDescription($node, "Noise Level"))


Best regards,
Victor

P.S. Can we move this discussion to the forum because this information may be useful for others?

This topic has been moved to Feature Requests.

https://www.netxms.org/forum/index.php?topic=272.0

Hello!

NetXMS version 0.2.20 is out. Changes since version 0.2.19:

* Implemented advanced event processing using situations
* Added checking of NetXMS server own network connectivity via beacon hosts
* Implemented "proxy node" functionality for DCIs
* Added possibility to use values of other DCIs in transformation scripts
* Added possibility to specify multiple recipients in e-mail or SMS action
* Implemented System.CPU.Usage for individual processors on Linux
* PING subagent: added parameter ICMP.PacketLoss(*)
* Command line options for the server changed to use common style
* Added UNICODE support in client part on Linux/UNIX
* Implemented macros in template DCIs (expanded when template applies to node)
* Added event storm detection
* Added possibility to specify multiple SNMP community strings for discovery and configuration polls
* NetXMS server now can understand interface aliases (description in Cisco terms)
* Added optional synchronization of node names with DNS
* New command line tool for managing alarms - nxalarm
* Implemented "stop processing" option for event processing policy rule
* Implemented "move" operation for templates (move between template groups)
* New internal parameter: ConditionStatus(*)
* NXSL:
   * Implemented condition operator (?
   * New built-in functions: gmtime(), localtime(), left(), right()
* Fixed issues: #188, #189, #190, #191, #195, #199, #203

Best regards,
Victor