NetXMS Support Forum

Hi,

it could be like this:


if ($object->type == 1)
   return true;  // allow all subnets

parents = GetObjectParents($object);
//if (parents == null) return false;
foreach(p : parents)
{
   if ((p->type == 5) && (p->name == "containerA" || p->name == "ContainerB")) return true;
}
return false;


You can also add additional contraints on subnet names as usual using $object->name.

Best regards,
Victor

Line like this:


table = AgentReadTable($node, "System.Processes");


will read agent table (System.Processes in this example) into variable. It will be object variable of class Table. Then you can walk through table using it's methods. For example, to read value of column "NAME" in first row you can use the following code:


colIndex = table->getColumnIndex("NAME");
value = table->get(0, colIndex);


You can iterate through table using rowCount attribute as stop indicator:


for(row = 0; row < table->rowCount; row++)
{
   value = table->get(row, colIndex);
}


Best regards,
Victor

P.S. If you meant transformation script of a table DCI, then you don't need to read table - variable $1 will hold table object.

Just fixed it. Fix will be included in 2.0-RC1.

Best regards,
Victor

I probably understand it - nodes on L3 map re connected via subnet objects, not directly - and you filtered out subnet objects. You should change your filter to allow subnets or add relevant subnet objects to your container.

Best regards,
Victor

Did you check connector color in map properties? By objects' locations it seems that they are connected but connectors are invisible.

Best regards,
Victor

currently all scripts are handled equally - so it doesn't matter if script is a network map filter or DCI transformation script for example. Reason is the same - imagine you have access only to network map object - if script do not have access checks you'll be able to access data for nodes you don't have access to. I thinking for some time already about more sophisticated access control within scripts, but don't have better solution yet.

Best regards,
Victor

Hi,

links are not affected by map filter. Did you layout nodes by hand? If not, it seems as if links are there but just invisible. Just in case - check link color in map properties.

Best regards,
Victor

Hi,

these DCIs are not supported anymore because of recent changes in server internals. There are no more separate queues for status and configuration pollers - from 2.0-M5 we are using dedicated thread pool with task queue instead. You can safely delete these DCIs. If you are interested in monitoring poller thread pool, you can configure the following internal DCIs on server node:

Name: Server.ThreadPool.LoadAverage(POLLERS)
Description: Thread pool POLLERS: load average 1 minute

Name: Server.ThreadPool.Load(POLLERS)
Description: Thread pool POLLERS: current load

Name: Server.ThreadPool.CurrSize(POLLERS)
Description: Thread pool POLLERS: current size

Best regards,
Victor

Hi,

you can use scripting to store timestamp of first event in node's custom attributes, and for each subsequent event chech if it is too close to original one and only pass through if interval between them is sufficiently large.

Best regards,
Victor

Can you please send me config.log and output of command

ldd /path/to/nxdbmgr

Best regards,
Victor

Инсталлер агента поддерживает unattended install: https://wiki.netxms.org/wiki/Agent_Installation_Guide#Unattended_installation_of_NetXMS_Agent_on_Windows.
Можно либо настроить запуск инсталлятора удаленно, либо сделать простой msi пакет который будет просто запускать инсталлер с нужными ключами.

Change should be instant. Another issue could be opened data collection editors for nodes - while data collection for node is open, server will not apply template changes. If this is not the case, then there is serious bug that needs additional debug.

Best regards,
Victor

Hi,

you do not need auto-apply script to propagate changes on nodes where template already applied. Changes in template will be propagated on all related nodes as soon as you close data collection editor for template.

Best regards,
Victor

Hi,

if interface set to "ignored" state it is ignored (as name implies). However, node still should be marked as down if it cannot be reached by any means (SNMP, ICMP, or agent). Do you have at least one interface set to expected state "up"?

Best regards,
Victor

Hi,

try to add configuration option --with-internal-libexpat when you run configure.

Best regards,
Victor