NetXMS Support Forum

Hi!

You can create another DCI for System.CPU.Count parameter and read it's value in transformation script by calling GetDCIValueByName($node, "System.CPU.Count"). Full script could looks like


return $1 / GetDCIValueByName($node, "System.CPU.Count");


Best regards,
Victor

Думаю что можно будет. Добавил в feature requests: https://www.radensolutions.com/chiliproject/issues/368

А можете stack trace прислать (команда bt в отладчике после получения SIGSEGV)?

Sorry, not yet. At some point I completely forgot about it I've added a bugtracker issue (https://www.radensolutions.com/chiliproject/issues/367) so it will not be forgotten next time.

Best regards,
Victor

Hi!

Yes, you can create node object and then define DCI with data really being collected from another node. You should set "proxy node" property in your DCI to the node where data collection really occurs. For example, you have server node (MGMT) and monitored node (TARGET). You configure PING subagent on node MGMT. Then create DCI for ping subagent on node TARGET with proxy set to MGMT. It will collect data from MGMT, but it will be associated with TARGET.
You have to add node where you create proxied DCI to proxy node's "trusted nodes" list, or turn off trusted nodes checking by setting server configuration variable CheckTrustedNodes to 0. A bit more detailed explanation of trusted nodes concept is here: http://wiki.netxms.org/wiki/SG:Security_Issues.

Best regards,
Victor

You cannot measure latency or packet loss with method 1. If you need it, you should use method 2.

Best regards,
Victor

Hi!

You can use instance discovery for that. For example, to monitor input bytes on all interfaces, create DCI (either directly on node or in template) with SNMP OID set to

.1.3.6.1.2.1.2.2.1.10.{instance}

and on "Instance Discovery" page choose SNMP Walk - Values as discovery method and enter .1.3.6.1.2.1.2.2.1.1 as SNMP OID.

Best regards,
Victor

Hi!

Rule should looks like this:


<rule>
   <match>^\[INFO \]\[SERVER\] (.*)</match>
   <event params="1">event code here</event>
</rule>


Best regards,
Victor

Hi!

You still need winperf subagent if you need some standard agent parameters, like System.CPU.Usage. But you can remove all pre-configured counters in nxagentd.conf.

Best regards,
Victor

Hi!

Please show exact command line you are using. Also, common problem is that you start agent under non-root account and it does not have write access to log file given in nxagentd.conf.

Best regards,
Victor

Hi!

Run nxdbmgr with -X command line option. Also, I'll repack installers so they will create correct DB schema - you'll be able to upload updated installer in few minutes.

Best regards,
Victor

Hi all!

NetXMS version 1.2.9 is out. Changes since previous release:

- Templates can be applied on clusters
- Filters for automaticaly populated network maps
- User-defined constants in NXSL
- New methods deleteColumn and deleteRow in NXSL class Table
- New NXSL functions: chr, ord
- HTTPS support in port checker subagent
- Added MIBs for Nortel/Trapeze Wireless security switches
- New MIBs: BAY-STACK-NOTIFICATIONS-MIB, SUN-HW-CTRL-MIB, SUN-HW-TRAP-MIB, SUN-PLATFORM-MIB
- Management console:
   - New dashboard elements: status map and table value
- Fixed issues: #202, #300, #304, #305, #309, #311, #325, #327, #332, #334, #335, #336, #337, #338, #339, #340, #342

Best regards,
Victor

Hi!

There are no built-in tool to do this. However, you can configure external script to be executed when you got error 3, and use wget or similar tool to store page content into a file.

Best regards,
Victor

Hi!

Starting from version 1.2.9, you can configure web session timeout in nxmc.properties file.

Best regards,
Victor

Hi!

You don't need to configure instance discovery - this is why data not being collected. Setting instance discovery method to "None" should help.

Best regards,
Victor