NetXMS Support Forum

Hi!

I agree that this is needed. I'm thinking of adding "default icon type" option to "Map Options" property page for map object. Issue in bug tracker to track: https://www.radensolutions.com/chiliproject/issues/204.

Best regards,
Victor

Upd: в аттаче SQL скрипт для конвертации таблицы event_log в правильный формат.

Оффтопик: кто-нибудь может дать мне invite для регистрации на хабрахабре? Если да, то пишите в личные сообщения.

Hi!

It's not possible to specify such relation manually. Anyway, it is layer 2 connectivity issue, not layer 3, as both nodes (physical host and VM) are in same subnet, so 192.168.1.10 is not involved in the routing process, but acting as Ethernet bridge. I will add a feature request for including layer 2 topology into event correlation process.

As a workaround, you can check status of the host node in the script in event processing policy, but this may not work as expected if VM polled first (so server don't know that host is already down).

Best regards,
Victor

Похоже что изначально таблица была создана с опцией ANSI_NULLS = OFF (так было по умолчанию на старых версиях MS SQL). Единственный вариант похоже - это пересоздать таблицу EVENT_LOG заново с опцией ANSI_NULLS = ON. Одно из предлагаемых решений: http://stackoverflow.com/questions/10010042/update-ansi-nulls-option-in-an-existing-table.
На всякий случай - DDL для создания таблицы:

CREATE TABLE event_log
(
event_id bigint not null,
event_code integer not null,
event_timestamp integer not null,
event_source integer not null,
event_severity integer not null,
event_message varchar(255) null,
root_event_id bigint not null,
user_tag varchar(63) null,
PRIMARY KEY(event_id)
) ;
CREATE INDEX idx_event_log_event_timestamp ON event_log(event_timestamp);


Microsoft про ANSI_NULLS: http://msdn.microsoft.com/en-us/library/ms188048.aspx

Hi!

In 1.2.5 we improve event correlation based on topology, so if NetXMS knows full path between itself and remote node it should correlate events automatically and only pass NODE_DOWN event for router. You can check this by selecting management server node object in object tree, then select "IP Route" from context menu, select remote node, and check that correct IP path is shown.

Sorry, I didn't fully understand web site question. Can you give a simple scenario please?

Best regards,
Victor

Отличие статуса Resolved от Terminated в том, что аларм остается видимым в консоли, хотя и не оказывает влияния на статус хоста. В нокоторых организациях это используется для того, чтобы сменные операторы видели недавнюю историю. Например, при автоматическом решении проблемы можно в event processing policy использовать resolve alarm вместо terminate alarm - тогда оператор видит, что проблема была и уже решена, и может вручную сделать terminate. Т.е. теперь у аларма 4 состояния: Outstanding -> (Acknowledged) -> (Resolved) -> Terminated.

Hi all!

NetXMS version 1.2.5 is out! Changes since previous release:

- Topology-based event correlation improved
- Network discovery improved
- Mapping tables
- New NXSL functions: ceil, floor, round, format, map
- Management console:
   - "Alarm Details" view
   - "Area" option implemented on line charts
   - Multiple DCIs can be combined on one graph on "Performance" tab
   - New dashboard element: separator
   - DCIs can be created from MIB Explorer
   - Textual conventions for selected MIB object displayed in MIB explorer
   - Fixed bug with chart titles in dashboards
   - "Snap to grid" and "Align to grid" options in network maps
   - Improved Y-range adjustment in line charts
   - Improved tooltips in line charts
   - Custom logo can be set on login screen in web console
   - Fixed performance and stability issues with image library
- Android client:
   - Select all/unselect all in alarms list
   - Multipliers for graphs and last values: binary (power of two) and decimal (power of ten)
   - Show number of pending alarms in home screen
- API for creating embedded application agents
- Initial (alpha) version of mobile agent for Android devices
- Fixed issues: #23, #47, #49, #131, #154, #162, #163, #172, #175, #177, #178, #180, #186, #187, #188, #189, #192, #196

Best regards,
Victor

There are no much development documentation yet. Just ask me on forum and I'll provide an answer.

Best regards,
Victor

Мне как программисту нынешнее поведение скриптов трансформации казалось логичным Однако данное предложение думаю действительно уменьшит количество недопониманий и и ошибок. Сделал что если скрипт не возвращает значения или возвращает null, то значение DCI не изменится.

Hi!

You can get history of events via event log viewer (View -> Event Log).

Best regards,
Victor

Hi!

Thank you! You can send me output of nxsnmpwalk on OIDs mentioned before:

.1.3.6.1.2.1.1
.1.3.6.1.2.1.2
.1.3.6.1.2.1.17.1
.1.3.6.1.2.1.4.20.1
.1.3.6.1.4.1.9.9.401.1
.1.3.6.1.4.1.9.9.134.1
.1.3.6.1.4.1.9.9.276.1
.1.3.6.1.4.1.9.9.173.1
.1.3.6.1.4.1.9.9.128
.1.3.6.1.4.1.9.9.68

You can send them to [email protected].

Best regards,
Victor

For counting processes there are separate parameter Process.CountEx, which has two arguments - process name and command line, both are regular expressions.

Wiki is supposed to be most up-to-date information source, but unfortunately it still missing lot of information, including detailed description of agent parameters. We are updating wiki, but it's a slow process.

Best regards,
Victor

Hi!

You can specify command line filter in all Process.* parameters. Full syntax of Process.CPUTime (and others Process.*) is following:

Process.CPUTime(process, type, cmdline)

Where

process - process name. If cmdline is not given, only processes with matched name will be counted and read. If cmdline is given, process interpreted as regular expression.
type     - representation type (meaningful when more than one process with the same name exists). Valid values are:
         min - minimal value among all processes named <process>
         max - maximal value among all processes named <process>
         avg - average value for all processes named <process>
         sum - sum of values for all processes named <process>
cmdline  - command line (regular expression to match).

So to match all processes named qemu-kvm with word test in command line, you can use

Process.CPUTime(^qemu-kvm$, sum, test)

Don't forget that both process name and command line are regular expressions when extended format is used, so if you use "qemu-kvm" as process name (without ^ and $), processes contained this in the name (like qemu-kvm2) will also be matched.

Best regards,
Victor

Hi!

What you mean by "disappeared"? It stops collecting data, or configured schedule really disappears from DCI configuration?

Best regards,
Victor