I was not able to replicate this. What kind of ID do you have in m variable, is it decimal number or hex? I'd try a few things: executing this script via "Execute server script" from node context menu. May be you'll see some errors there. you can try removing the dot from the beginning of custom attribute name - in this case custom attribute will be visible in node properties. Does setCustomAttribute actually add custom attribute to the node?

Normally it should happen automatically for events SYS_NODE_DOWN if topology is known to the server. If server is able to determine route from itself to unreachable node, it will check all intermediate nodes, and generate SYS_NODE_DOWN only for router closest to the server, and SYS_NODE_UNREACHABLE for nodes down the line. For more complex logic you can use script filters - all kind of topology information is available in scripts, so you can filter events based on peer nodes, routing information, etc. Best regards, Victor

SMTP Authentication was added in 4.3, please see updated documentation: https://www.netxms.org/documentation/adminguide/event-processing.html#notification-channels

SMTP Authentication was added in 4.3, so now it should work without email forwarder. Please see updated documentation: https://www.netxms.org/documentation/adminguide/event-processing.html#notification-channels

SMTP Authentication was added in 4.3, so now it should work without mail relay software. Please see updated documentation: https://www.netxms.org/documentation/adminguide/event-processing.html#notification-channels

SMTP Authentication was added in 4.3, please see updated documentation: https://www.netxms.org/documentation/adminguide/event-processing.html#notification-channels

SMTP Authentication was added in 4.3, please see updated documentation: https://www.netxms.org/documentation/adminguide/event-processing.html#notification-channels

@victor said in Help: H3C port security policy causes the switch to fail to learn the interface: I've added processing of FDB record status 6 - next patch release should process them in a same way as status 3 (dynamic). Best regards, Victor The problem has been solved in the just released version 4.3.6, thank you very much!

dciId = 2531; threshold = 500 * 1000 * 1000; t = localtime(); t->hour = 0; t->min = 0; t->sec = 0; endTime = mktime(t); if (t->mon >= 2) { t->mon = t->mon - 1; } else { t->mon = 12; t->year = t->year - 1; } startTime = mktime(t); a = GetDCIValues($node, dciId, startTime, endTime); HighCnt = 0; Cnt = 0; for (v : a) { Cnt++; if (v > threshold) HighCnt++; } return HighCnt / Cnt; Here's an example script that grabs all values for a DCI for last month. You can put this in a script DCI that is being collected by cron schedule on the first day of each month. Once you nave array with values, you can do various calculations with them. If you want to do calculations that involve big numbers, e.g. calculating average value, initialize variable like that: TotalCounter = 0L; This will use INT64 for this variable.

Yes, URL field supports macros, so %[OGAckAlarmID] should work. I am not sure how you are getting alarm ID in that script, may be you should pass the ID as parameter in your PostEvent() calls. Request Data field is employed when web service is used as data source for a DCI. When using post() method of web service object, that field is ignored, so you have to pass the whole request in post() call.

Resolved

I probably do not completely understand what the issue is. Configuration looks correct, you set "Name" column as instance column, not an "Index". But it should work both ways.

You should create local SQL account. It should be also possible to login with the same AD user NetXMS agent runs under (in that case you should specify * as login name and password is not needed).  Best regards, Victor

Thank you so much...

Currently it's not supported. There are plans to implement it, but it's not clear how soon this could be. If, just in case, your company wants to sponsor this development, feel free to contact us.

It works normally now, thanks

Hi Victor, Upgrading to 4.3.4 did indeed fix the PushDCIData() segfault problem I was seeing. Thanks for your help.

Hello, I apologize for late reply. Excluding potential infrastructure issues took longer than anticipated. After analysis of all crashes, issue was found to be associated with single debian/bullseye package update: old: lxcfs=4.0.12-pve1 new: lxcfs=5.0.3-pve1 Further analysis was not done. Upgrade of package causes segmentation fault, general protection faults in multiple nxagentd linked libraries that unfortunately manifest in multiple nxagentd failures, consequential local sqlite database corruption and associated 2nd level of errors. We observed crashes in: libnxsqlite.so, libc-2.31.so, libnetxms.so.43... Downgrading proxmox v7 lxcfs package to 4.0.12-pve1 resolved issues. thank you for your help and apologies for any inconvenience caused. Br, Aleš