NetXMS Support Forum

A prishlite pozalujsta config.log

Hi!

DCI object has the following attributes:

Attribute	Description
dataType	DCI data type (string, integer, etc.) represented as internal numeric code
description	DCI description
id	DCI identifier
lastPollTime	DCI last successful poll time as UNIX timestamp (number of seconds since 01.01.1970 00:00:00 UTC)
name	Parameter's name
origin	DCI origin (NetXMS agent, SNMP, etc.) represented as internal numeric code
status	DCI status (0 = active, 1 = disabled, 2 = not supported)
systemTag	DCI system tag (not available in 1.0.x versions)

So, you need lastPollTime attribute.

Please also note that there are new function called "trace", which can be very useful in debugging scripts. It takes two arguments - debug level (0 .. 9) and text, like this:

trace(1, "some message");

Text passed as second argument will appear in server's log, if given debug level less or equal current server's debug level (set by -D command line option). If debug level in trace() call set to 0, message will always be logged with INFO severity.

Best regards,
Victor

In 1.0.0-rc1 I have added new NXSL function FindNodeObject. It takes two arguments: current node object and ID or name of node of interest. It can be used as following:


sub main()
{
   // Search for node named "gateway"
   gw_node = FindNodeObject($node, "gateway");
   
   if (gw_node == null)
      return 0;   // No such node or access denied

   // from here, gw_node can be used in a same way as $node, for example:
   status = GetDCIValue(gw_node, FindDCIByDescription(gw_node, "Status"));

   return 1;
}


Best regards,
Victor

Hi all!

Version 1.0.0-rc1 is out. It's a release candidate for stable 1.0.0 branch. If it works fine, we release 1.0.0 and focus on active development of 1.1.0 branch, where lot of changes are planned. Also, preview of new Eclipse-based management console from 1.1.0 branch, compatible with current 1.0.0 branch, will be released soon.

Changes in 1.0.0-rc1 compared to 0.2.23:

- System configuration (events, SNMP traps, templates, event processing rules) can be exported and imported in XML format - this solves various problems with old NXMP files
- NXSL improvements:
   - New functions: GetDCIObject, GetInterfaceName, FindNodeObject, trace
   - Added built-in constants TRUE and FALSE
- Added support for encrypted DB passwords in netxmsd.conf
- Improved SNMPv3 support
- Fixed issues: #62, #278

Best regards,
Victor

По умолчанию на событие SNMP_LINK_DOWN аларм не создается. Надо добавить в event processing policy правило для генерации аларма по этому событию.

There are two parameters for disk space on UNIX: Disk.Free (or Disk.FreePerc) and Disk.Avail (or Disk.AvailPerc). First shows total amount of free space, including reserved blocks. Second shows free space available to non-root users - free space without reserved blocks. You should compare Disk.Avail results with df output.

Best regards,
Victor

Esli pri obrabotke sobitija, to dolzno rabotat' tak:

GetDCIValue($node, FindDCIByName($node, "Disk.Total(" . $6 . ")"));

Unfortunately, PocketPC version is long forgotten. Probably I could rebuild it to work with current server version, but it has very limited functionality. You can:
- Browse object tree
- Work with alarms: see list, acknowledge and terminate
- View last collected values for DCIs
- View graphs for DCIs

If such functionality is interesting for you, I could try to rebuild PocketPC client.

Best regards,
Victor

It's I/O error on server - most likely server cannot access MIB file (netxms.mib). Did you compile MIBs?

Best regards,
Victor

Very strange. I can create a graph for a one year for example. Is there anything in server logs? Also, could you please run server with -D 9 for a moment, try to create graph for long period, and send logs to me (at [email protected])?

Best regards,
Victor

He probably mean menu in SQLite Database Browser, not in NetXMS console.

Best regards,
Victor

What do you mean by that? There are various places where scripts could be used - autobinding, data transformation, event processing, etc. What do you want to achieve?

Best regards,
Victor

Hi!

You should create separate events (for example, DISK_SPACE_WARNING, DISK_SPACE_CRITICAL) for each level you wish to have. Then add appropriate thresholds and set your custom events as activation events. For example, for threshold "> 50" set  DISK_SPACE_WARNING as event, and for threshold "> 90" set DISK_SPACE_CRITICAL as event. Don't forget to order thresholds properly - in case with disk space, you should start with "> 90", then "> 75", then "> 50". See data collection section in manual for explanation. Add appropriate processing to event processing policy.

Best regards,
Victor

You have to options:
1. Convert DCI values to MB on collection time via transformation script;
2. Create separate event for disk space threshold violation, and instead of %4 macro (which is expanded into actual values) call script which will convert this value to MBs.

Best regards,
Victor

Hi!

If you really need alert every hour for every host, you can create two thresholds for "Status" DCI covering all possible values (for example, one for "equals 0", other for "not equals 0"), configure it to send same event on activation, and set repeat interval to 3600 seconds. Then add processing for generated event as usual. You will have this event generated every hour.

Best regards,
Victor