Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Victor Kirhenshtein

#3676
General Support / Re: Log parsing
May 12, 2014, 07:55:23 PM
I'm a bit lost - are you sure this is log for parser mentioned in the beginning? From this log file I see that parser correctly found matching line (using StatusPoll.* pattern) and generate event. Parser in the first post had different matching pattern. Let's try to combine everything related in one post - server log and agent log for same time period plus actual parser definition.

Best regards,
Victor
#3677
General Support / Re: GetDCI
May 12, 2014, 07:50:04 PM
Script looks correct. Could it be that disk E: has non-zero total space (could be the case if this is CD drive with disk inserted or any other read-only device)?

Best regards,
Victor
#3678
Судя по сообщениям об ошибке (ПРЕДУПРЕЖДЕНИЕ:  нехватка разделяемой памяти), проблема в настройках PostgreSQL сервера. Увеличте размер shared memory, должно помочь.
#3679
Hi,

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

Best regards,
Victor
#3680
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
#3681
Can you please show how exactly problematic threshold looks like?

Best regards,
Victor
#3682
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
#3683
Currently you cannot see what output agent was gathered nor measure response time. Feel free to fill feature request :)

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

Best regards,
Victor
#3685
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
#3686
General Support / Re: Distributed Monitoring
May 08, 2014, 05:33:10 PM
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
#3687
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
#3688
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
#3689
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
#3690
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