NetXMS Support Forum

Hi,

but desktop console can connect? Try to find log file on web UI (it is called .log and should be within application's working directory - in my case it is /var/lib/tomcat7/work/Catalina/localhost/nxmc/eclipse/workspace/.metadata/.log).

Best regards,
Victor

Hi,

wheezy should be available now as well.

Best regards,
Victor

You cannot show tooltips non-interactively. However, you can put DCI values on a map using DCI container decoration. Or you can use DCI image and use transparent image when threshold not active and non-transparent image with service information when threshold is active.

Best regards,
Victor

Добавил в 2.0.5 и 2.1-М1 (вместе с атрибутами source и sourceId).

Во всех скриптах где есть $event (EPP filter и script action) есть переменная $object, которая указывает на источник события. Добавить источник как атрибут самого события тоже не проблема конечно.

64 битные счетчики добавлены в 2.0.5 и 2.1-М1.

Hi,

I've fixed that, fix will be included in 2.0.5 release.

Best regards,
Victor

Hi,

proper solution will include changes on agent side. I'll change the agent so it will save parameter names in local database so if server request comes before provider first run agent will respond with collection error instead of unsupported parameter.

Best regards,
Victor

Hi,

currently it is not possible.

Best regards,
Victor

Hi,

currently it's possible only by replacing normal DCIs with script DCIs (script DCI call SNMPGet and on failure returns something to indicate a failure). I'll add feature request to make this functionality simpler.

Best regards,
Victor

Hi,

basically in a same way, just use different file names:

C:\NetXMS\bin\nxmibc.exe -z -d C:\NetXMS\share\mibs -o C:\NetXMS\var\netxms.mib

(assuming NetXMS is installed into C:\NetXMS).

Best regards,
Victor

Hi,

you can mark DCI to be shown in object tooltips (on "Other options" page in DCI properties). You can also add DCI display information to network map using "DCI container" or "DCI image" decorations.

Best regards,
Victor

Hi,

could you please be more specific? What is your configuration file, what errors you get?

Best regards,
Victor

Hi,

added as feature request: https://dev.raden.solutions/issues/1247. I'll try to implement it in 2.1 branch.

Best regards,
Victor

Hi,

I see that there are 7340 parameters configured for collection. Strange enough some seems to be duplicates, because there are only 6966 distinct names - but all have different DCI IDs. Is it really that much DCIs on this node? Most of them seems to be external parameters. How long this script executes? Because if there are enough long-running scripts it can overload data collection thread pool and possibly cause other strange effects. I will try to simulate collection of that many external parameters and see if I will be able to reproduce strange behavior you observed.

Best regards,
Victor