NetXMS Support Forum

Hi!

You don't need to use situations here, and you didn't add actual check for service. You should go to data collection for node where you want to monitor spooler service, and add new parameter with source NetXMS agent and name System.ServiceState(Spooler). Then you should add threshold for that parameter (on Thresholds tab) with condition "last value not equal 0" and set activation event to SPOOLER_DOWN. Then it should work.

Best regards,
Victor

Hi!

You should specify database id when reading Oracle-specific parameters. In your config database id is DB1, so you should specify parameters as

Oracle.DBInfo.IsReachable(DB1)
Oracle.DBInfo.Name(DB1)

and so on. List of available parameters can be found here: http://wiki.netxms.org/wiki/Oracle_Monitoring_Subagent.

Best regards,
Victor

Hi!

Can you please send me content of your /proc/net/dev file?

Best regards,
Victor

That's very strange. When possible, can you stop the server and run database check? Will it report any errors?

Best regards,
Victor

Hi!

Your findings are correct. I'm personally only encounter switches reporting full FDB via dot1dTpFdbTable, but using dot1qTpFdbTable when possible seems more correct. I'll fix that for next release.

Best regards,
Victor

It should be resolved already in 1.2.1. I'll double check this.

Best regards,
Victor

Da.

Sorry for deley with that. I'll spend few evenings on this and next week and will convert most plugins to use messages files. Then you will be able to continue translation.

Best regards,
Victor

Я думаю что можно использовать custom attributes. Их значения можно использовать в NXSL скриптах и Event Processing Policy, получить через API или прочитать напрямую из базы.

Добавил параметр --disable-lmsensors  в configure.

Hi!

Idea is good. I have added it to feature requests, but I cannot promise exact version when it will be implemented.

Best regards,
Victor

Hi!

Is it possible to unmanage all nodes for some time and see if memory consumption is growing? If it stops growing, then set managed state for nodes one by one or in groups of similar nodes, and see after what node/group memory consumption starts growing again?

Best regards,
Victor

Hi!

It's not possible now. Main concern here is that object tool filtering is done on client, which doesn't have information about actions configured on agent. Implementing filtering on actions actually configured on agents will require either additional round-trip to server on each context menu opening (which can slow down UI) or synchronizing this information with client. I'll think what can be done here, because idea by itself is good.

Best regards,
Victor

Are you 100% sure that they are nowhere in the tree? Try to do IP address filter in object tree - enter > followed by IP address in filter field.

Best regards,
Victor

Quote from: kozlov_ao on June 21, 2012, 10:43:32 PM
Эээ..ммм.. а почему русские?
мы же вроде переводим счетчики на английские?

Наоборот - мы переводим переданные английские названия счетчиков в русские, которые нужны на локализованной системе.