NetXMS Support Forum

Hi,

most likely. It could be due to slow database response - you can check that by setting server configuration parameter LongRunningQueryThreshold to non-zero value - it will log all SQL queries with execution time longer than given number of milliseconds.

Best regards,
Victor

Hi,

you may try to increase value of server configuration parameter AgentCommandTimeout (it is in milliseconds).

Best regards,
Victor

If you use context menu it will extract currently selected DCIs. You can also use "export all" option in view menu (in top right corner).

Best regards,
Victor

P.S. Actually, for Windows servers you can use performance counters to get momentary CPU usage - select "Windows performance counter" as DCI source and configure appropriate counter.

Hi,

agent already calculates average for one minute, so you receive average value. If you collect it every second, you'll get it as sliding window, but still it will be average for last 60 seconds.  It is done that way because usually data collection do not happen every second to avoid excessive network traffic and load on the systems involved. Currently it is not possible to get 30 seconds average or momentary CPU usage values from agent.

Best regards,
Victor

Hi,

I see few options to improve this:

1) rename "Remove" option on template to "Remove from node" (or something similar that will not imply destruction of template itself);
2) add context menu option "remove from template" to node under template, which will remove node from that particular template.

Best regards,
Victor

Hi,

yes, it is bug in FindObject (fixed in 2.0.5). Anyway, it may not be a good idea to use FindObject - because it finds objects globally, while you need interfaces from that specific node. You can add the following function to your script to get interface by name:


sub FindInterfaceByName(node, ifName)
{
foreach(i : GetNodeInterfaces(node))
{
   if (i->name == ifName)
      return i;
}
return null;
}


and use it like this:


iface = FindInterfaceByName($node, "Se1/0");


Best regards,
Victor

Implemented in 2.1-M1 (agent will be compatible with 2.0.5 server).

Best regards,
Victor

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