Automatic Apply Rule for template not working

Reply to Automatic Apply Rule for template not working on Thu, 23 Sep 2021 20:06:02 GMT

ChrisC — Thu, 23 Sep 2021 20:06:02 GMT

Thanks, it was the "\" causing the problems.
Once I found the contents of println $node->snmpOID; for the node and use that, it applied with out problems.
Using "like" will also help for other templates I am trying to make.

Reply to Automatic Apply Rule for template not working on Thu, 23 Sep 2021 11:49:15 GMT

victor — Thu, 23 Sep 2021 11:49:15 GMT

Hi,

\ is an escape character in NXSL string, so for actually passing \ to regex processor, you can escape it, like this: "^\\.1\\.3\\.6".

In simple cases you can use like instead of regexp matching. For example, to match all OIDs starting with .1.3.6.1.2.1 you can use condition

if (oid like ".1.3.6.1.2.1.*")
{
   /* match, dio something */
}

Best regards,
Victor

Reply to Automatic Apply Rule for template not working on Fri, 17 Sep 2021 10:32:01 GMT

Filipp Sudanov — Fri, 17 Sep 2021 10:32:01 GMT

In context menu of that node you can select "Execute server script" and try your script there; The node that you right-clicked will be available as $node, so all the attributes will be there.
You can do

println $node->snmpOID;

to see what's actually in there.

Match operation ~= looks to be correct, but you could just use simple comparison with == , then you'd not need to escape with backslashes.
In out-of-the-box templates there's e.g. SNMP->UPS->APC that has automatic apply rule that is checking some SNMP data.

The other debugging approach is to use
PollerTrace("your text");
or
trace(0, "your text");
First one will produce debug output in nxmc when you do Poll-> Configuration poll from node context menu.
Second will put debug to server log (at debug level 0 in this example)