NetXMS Support Forum

I'm working on it.

Best regards,
Victor

Not in the near future, because our time mostly goes to more important core features and Linux console. I can provide help if somebody will write that, but I will not be able to do it myself - only because of lack of time.

Best regards,
Victor

It's still there unfortunatelly... We have half-done code for event log monitoring, which was frozen some times ago due to lack of free time.

Best regards,
Victor

Hello!

Looks correct. Do you have any problems with it? Also, since version 0.2.20 you can collect total amount of RAM as separate DCI and use it's value in calculation instead of hardcoded value.

Best regards,
Victor

Is there any messages in agent's log (or system event log) when agent starts?

Best regards,
Victor

Hello!

Both are not possible now, but already put in wishlist by many people.

Best regards,
Victor

Hello!

Looks like a bug in MIB compiler. As a workaround, just comment out or delete entire DEFVAL line - it is not used by compiler anyway.

Best regards,
Victor

Correct way should be by adding --with-nxhttps to configuration line, like
./configure --with-server --with-agent --with-mysql --with-nxhttpd
I'll check this on my machine, but it should work...

Best regards,
Victor

Sounds quite strange. How nxhttpd.conf looks like and what type of system you are running on?

Best regards,
Victor

Hi!

Built-in actions System.Shutdown and System.Restart only available on Windows platform. On UNIX'es, you should define them manually in nxagentd.conf like this:


Action = System.Shutdown:/sbin/halt
Action = System.Restart:/sbin/reboot


Best regards,
Victor

Счетчик алармов увеличивается если у алармов совпадают ключи. Надо делать ключ на основе DCI ID, скажем добавлять _%5 к ключу.

Hello!

This can be done with alarm keys. When you creating alarm from NETWORK_PRINTER_DOWN event, set key for it to something like PRINTER_DOWN_%i (%i will be expanded to node's unique identifier - complete list of possible macros can be found in user's manual). Then, create rule for opposite event, and in alarm column for it, select "Terminate alarm with given key", and enter the same key.

Best regards,
Victor

From messages:

Quote from: Rando on April 11, 2008, 02:47:38 AM
Sorry, I didn't read the last part of the message.  Yes, you can transfer this to the forum.  I'm still struggling with the scripting.  Is there any examples with descriptions I can look at to see the structure and usage?  I'm just going through the manual right now.

Quote from: Victor Kirhenshtein on April 07, 2008, 04:37:10 PM

Quote from: Rando on April 07, 2008, 09:19:18 AM
I'm still learning the NetXMS software and have a wireless base station and remote wireless radios which is SNMP capable and I do get a signal value and a noise value.  For me to calculate the signal to noise ratio I have to subtract these two numbers to create a 3rd value that I would need to track.  Is there any way NetXMS can do this?

Yes, it's possible. You should define two DCIs, one will collect signal value, and other noise value. Then, for one DCI you can create transformation script, which will access last value of other DCI and use it in transformation. You can access other DCI value using built-in functions GetDCIValue and FindDCIByName or FindDCIByDescription. See user's manual for description of these functions (section 8.5.3).
You script may looks like following (assuming that you are transforming signal value and your noise DCI called "Noise Level"):

Code Select Expand


$1 - GetDCIValue($node, FindDCIByDescription($node, "Noise Level"))


Best regards,
Victor

P.S. Can we move this discussion to the forum because this information may be useful for others?

Could you please check attached WINPERF subagent - it should fix System.Uptime and System.ThreadCount on non-english systems.

Best regards,
Victor

Quote from: xenth on April 10, 2008, 05:42:21 PM
The value returned by agent on hdd space:

System #1: Free:62.7GB     NetXMS reads out: 67G
System #2: Free:8.64GB     NetXMS reads out: 9284M

It's a console display problem, not an agent bug. Actual DCI value for free disk space is in bytes. When you use multipliers in console to view current DCI values, console uses them in common sense, i.e. K = 1000, M = 1000000, and so on, because console has no knowledge about units of DCI - is it bytes or something else. If you multiply 62.7 to 1024 * 1024 * 1024 and then divide by 1000000000 and take whole part, you'll get 67. You can also turn off multipliers and see correct number of bytes.

Thre are no straight-forward solution for this. Probably we should add additional DCI property - units, to give console a hint how to work with the values.

Best regards,
Victor