NetXMS Support Forum

Hi,

!= null should work. Can you show full script please?

Best regards,
Victor

Hi!

Actually, if node is compoletely down, and SYS_NODE_DOWN event is generated, all SYS_IF_DOWN and SYS_SERVICE_DOWN events should be correlated to SYS_NODE_DOWN and not cause message sending. However, if node is not down completely, you may get lot of events and notifications if multiple interfaces goes down for example. The only way to create digest messaging is to write your own script which will do that. For example, you may store event messages into text file in event processing policy (using "execute" type action) and run cron job every 5 minutes to send this file as email if it is not empty.

Best regards,
Victor

Can you please show how exactly problematic threshold looks like?

Best regards,
Victor

Hi!

It's definitely a bug - looks like threshold state was not saved across restarts, although it had to be. I'll check this.

Best regards,
Victor

Currently you cannot see what output agent was gathered nor measure response time. Feel free to fill feature request

Best regards,
Victor

Yes, that change already applied - so after upgrade to 1.2.14 you'll get this problem fixed as well.

Best regards,
Victor

Hi!

Could you check what is returned by underlying SQL query? Implementation of this function tries to parse value read from database as double, so there should be no limitation on 32bit integer size.

Actual query is

SELECT avg(coalesce(idata_value,0)) FROM idata_<node_id_here> WHERE item_id=<dci_id_here> AND (idata_timestamp BETWEEN <time1> AND <time2>);

Best regards,
Victor

Hi!

Currently we do not support configuration synchronization between two NetXMS servers (although we have this in roadmap). What is possible now is event forwarding from one NetXMS server to another.

Best regards,
Victor

Hi!

If topology information is correct, you can try to use this script: http://wiki.netxms.org/wiki/Script_Example:_Additional_Information_About_Connected_Node as an example of how to get connected nodes and for SYS_NODE_DOWN event check if node is connected to the switch which is already down.

Best regards,
Victor

NetXMS agent uses PDH API to access performance counters. You can add feature request to our bug tracker for instance discovery support for perf counter DCIs.

Best regards,
Victor

Hi!

You can create filtering script for instance discovery which will attempt to get total space for file system and only return true if data was read successfully and size is non-zero. It could be something like this:


value = AgentReadParameter($node, "FileSystem.Total(" . $1 . ")");
return (value != null) && (value > 0);


Best regards,
Victor

Description of node class is here: http://wiki.netxms.org/wiki/NXSL:Node and all scripting reference information is here: http://wiki.netxms.org/wiki/Scripting_Guide

Best regards,
Victor

Hi!

WMI (stands for Windows Management Instrumentation) is not Windows Performance Counters - it's two different things. First you should understand what exactly you want to use. From the name \PhysicalDisk({instance})\Disk Reads/sec I suppose you are trying to use Windows Performance Counters. In this case, instance discovery will not work because DCI origin is not agent. It could be a feature request, but currently it's not possible.

Best regards,
Victor

No, it's not due to apostrophe character and SQL injection is not possible here. You can see that SQL statement is a prepared statement with placeholders - it is not constructed dynamically from external data. Also, error message clearly states "Violation of PRIMARY KEY constraint 'PK__alarm_ev__E6249E6BFEDA1E4D'. Cannot insert duplicate key in object 'dbo.alarm_events'. The duplicate key value is (1704, 64513)" - actual problem is that system for some reason tries to insert duplicate record into table. It is definitely a bug, but not a security threat.

Best regards,
Victor

Добавить все устройства из подсети во временный контейнер (если они уже не добавлены в какие-то контейнеры), после чего удалить субнет с неправильной маской и сделать configuration poll (или подождать). Потом временный контейнер можно будет удалить, он нужен чтобы при удалении субнета не удалились хосты.