NetXMS Support Forum

Please share what is your primary target for monitoring with NetXMS.

It's not exactly the same - using templates you cannot create DCIs depending on node capabilities (for example, enumerate all interfaces and create DCI for each interface).

Best regards,
Victor

Hi!

You must remove "always process all thresholds" option from thresholds and put "== 0" threshold first. Then you should get only one deactivation event. See this: http://wiki.netxms.org/wiki/UM:Data_Collection#Threshold_Processing for description why threshold order is important.

Best regards,
Victor

Если сами счетчики реально 32-битные (на хосте), то замена типа в NetXMS проблемы не решит - при переходе счетчика через 0 получится неправильное значение. Я еще проверю, какой тип данных для счетчиков использует операционная система. Если ето действительнно 32 битные, и траффик большой, то единственный вариант наверное - это делать опросы чаще, например каждые 10 секунд.

А какой CodePage стоит в netxmsd.conf? И что возвращает команда


nxget -l <windows_server_address> Net.InterfaceList


?

Hi!

Do they respond to SNMP? Check that SNMP settings are correct and that you can reach them by SNMP. You can do that using nxsnmpwalk or nxsnmpget tools.

Best regards,
Victor

Hi!

Both is not possible - you cannot run script on node, and you cannot create DCI from script. Idea is good, I'll add feature request for that (#219, #220).

Best regards,
Victor

Hi!

Can you send me a screenshot of DCI configuration (thresholds page) and event processing policy rules for threshold activation and deactivation events?

Best regards,
Victor

Будет в 1.2.6. Должно было быть в 1.2.5 уже

Обновленный скрипт для пересоздания таблицы event_log:


IF ((SELECT uses_ansi_nulls FROM sys.tables WHERE object_id = object_id('netxms.event_log')) = 0)
      BEGIN TRY
            BEGIN TRANSACTION;
            USE netxms_db;
            /*Create new table with identical structure but option on*/
            SET ANSI_NULLS ON;
            SET ANSI_PADDING OFF;

            CREATE TABLE netxms.event_log_new
            (
            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) not null,
            root_event_id bigint not null,
            user_tag varchar(63) not null,
            PRIMARY KEY(event_id)
            ) ;

            CREATE INDEX idx_event_log_event_timestamp ON netxms.event_log_new(event_timestamp);

            /*Metadata only switch*/
            ALTER TABLE netxms.event_log  SWITCH TO netxms.event_log_new;

            DROP TABLE netxms.event_log;

            EXECUTE sp_rename N'netxms.event_log_new', N'event_log','OBJECT';

            COMMIT TRANSACTION;
      END TRY

      BEGIN CATCH
            IF XACT_STATE() <> 0
              ROLLBACK TRANSACTION;

            PRINT ERROR_MESSAGE();
      END CATCH;
ELSE
      PRINT 'ANSI_NULLS ALREADY ON'


Quote from: Akira on January 16, 2013, 07:42:53 AM
С базой теперь ОК.
Теперь при старте консоли
Cannot load MIB file from server: Bad MIB file data

Попробуйте удалить файл netxms.mib из каталога $HOME/.nxmc/data и перезапустить консоль.

Hi!

I think you can ignore Java stuff for know and just use old console for editing XML. And yes, you must use &lt; for < character inside tag - and don't forget semicolon!

Best regards,
Victor

Hi!

I have marked legacy console as deprecated so new users will not try to download and use it. It is still required sometimes unfortunately, but many new things cannot be configured via legacy console. So I'm trying to avoid misunderstanding by new users.

Best regards,
Victor

Hi!

Sorry, these two parts are not covered and you still have to use legacy console for that. I'll try to fix that in 1.2.6 release.

Best regards,
Victor

Hi!

Agent policy places separate files into config include directory on agent. It will not change master configuration file of the agent. You can check manually that file with your configuration appears in config include dir on agent (in Windows it's usually C:\NetXMS\etc\conf.d).

Best regards,
Victor