NetXMS Support Forum

You can enable debug related to notification channels. This can be done without restarting server from Tools->Server Debug Console or from nxadm command line utility. Issue the following commands:

debug nc.* 6
debug ncd.* 6

You can check current status of debug by issuing

debug


Then check netxms server log file (/var/log/netxmsd on linux).

Hi!

I've checked with a developer yesterday - currently there might be issues with correlation for nodes that are behind proxy. This will be investigated whenever developer resources are available.

Looks like some screenshots are missing.
But a question regarding your text - may be you can just use your threshold script right on "Port Speed auf x/x/x" DCI?

This SNMP OID is a counter (https://oid-rep.orange-labs.fr/get/1.3.6.1.2.1.31.1.1.1.6). When setting up a DCI, on transformation tab select delta calculation - average delta per second.

Да, pinboard пока что не сохраняется. Месяцев через несколько наверное будет уже сделано

Должен быть отдельный пекедж netxms-agent-asterisk

There might be some changes recently on how agent handles actions - it might terminate them after some quite short time unless "action produces output" is enabled.
Can you please enable
DebugLevel=6
in agent config and share the log file for the moment when action is being executed?

P.S.
There's actually another approach that might help - In Configuration->Packages you can have executable or archive. When you select "Deploy package..." (in new nxmc this is done from context menu of nodes or containers), file will be uploaded and in case of executable it's possible to specify a command that will be executed. See docs for more info: https://www.netxms.org/documentation/adminguide/package-manager.html#

Ok. First thing to check - in node properties on Communication tab there is "Communication through external gateway". Is it unchecked for all these proxies and nodes?

What exactly version of NetXMS are you using?

You've executed  ldd oracle.ddr |grep 19 under root or some other user? nxagentd is probably running under root, which can have different env variables set.

For the agent config, you can specify env variables in [env] section, e.g.

[env]
ORACLE_HOME=/uat/db/19c
LD_LIBRARY_PATH=/uat/db/19c/lib

but I am not sure, if this affects database drivers, or only processes that agent launches after it has started (e.g. external metrics).

Historically SecondsToUptime() function was introduced before measurement units were added. So currently you can select  "Uptime" in measurement units and have it without transformation script. Threshold <= 600 should work.

Also, you can try threshold with function "Diff with previous value", 1 sample, < 0.

1) Yes, in action properties you can use e.g.

%n (%a) - %m

These macros will expand into NODE NAME (NODE IP ADDRESS) - MESSAGE TEXT FROM EVENT

Full list of macros is here: https://www.netxms.org/documentation/adminguide/event-processing.html#macros-for-event-processing

2) Pls show screenshots from DCI's properties (General and Transformation tabs). Right-click that DCI from the list and select "History" and share the screenshot of that. And also what is current value of uptime on that system.

You probably have "Epoch time" units selected for that DCI, which makes it display as Date and Time. But the actual value is Unix time - if you open history for that DCI, you would see the values. Threshold operation is happening with that unix time value.

So there's two ways how to do things:
a) in transformation script of that DCI:
return time() - $1;this way the DCI will have value of how many seconds ago the update last happened. You can use "Uptime" units to display that. And in threshold you would want to check if the value is bigger then 2592000   (which is 60 * 60 * 24 * 30).

b) or you can have it without any transformation, and use script threshold:
return time() - $1 > 2592000;
or even
return time() - $1 > $2 * 3600 * 24;
and specify the threshold value in days in "Value" field of threshold properties.

XPath was added in 4.5.0, so you can try using this.

Community string from node properties is used for read operations during polls and data collection.

Write operations, as far as I know, could be performed from NXSL scripts only and in createSNMPTransport method (https://www.netxms.org/documentation/nxsl-latest/#_instance_methods_13) you can specify custom community string. You can store this community string in a node custom attribute.