NetXMS Support Forum

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.

Yes, threshold script is a better place for this.

If you open hint in editor of threshold script, you'll see:
$1 current DCI value;
$2 threshold value;
$dci this DCI object;
$isCluster true if DCI is on cluster;
$node current node object (null if DCI is not on the node);
$object current object.

So you can use $1 instead of GetDCIValueByDescription($node, dciDescription);, this would give you current value of the DCI.

GetDCIValueByDescription() actually gets previously collected value, when server starts, values for frequently collected DCIs are not cached from database to memory, that's would explain script error.

Hi!

Yes, absolutely. You just need to make your data collection items (DCIs) in a template. The you would apply the template to the node (you can select container when applying, in this case template would be applied to all nodes under that container).

It's also possible to automate template application - you can check in out-of-the-box templates, e.g. Operating Systems -> Windows - in properties of it there's Automatic Apply Rules.


Also, we've recently published a half-hour long recording of NetXMS Demo session - this might be helpful to see what are the capabilities of the system:
https://www.youtube.com/watch?v=QhHznyOXEFk

There are agent metrics for that, e.g.
File.Time.Modify(/etc/passwd)

https://www.netxms.org/documentation/adminguide/appendix.html#file-time-modify

Metric would return unix time.


First thing is to create Data Collection Item on a node with that metric.

Then you can add threshold, if you need a notification when modification time changes, you can use function "Diff with previous value", operation "!= : not equal to".

Then rule in event processing policy is needed, we can discuss this later on.

Hi!

In properties of map object on Map Appearance tab there's Drill-down object field where you can select the dashboard.
This setting is saved in node's (or other object properties), so if node is placed to another map this setting there will be same.

Few thousands should not cause any problems. 

The other options could be to use custom attributes on corresponding nodes - this is a bit cleaner solutions, as when a node is deleted, custom attributes are deleted as well, while persistent storage might still have some remaining entries. If you go that way, it's better to use custom attributes with names starting from $ sign - it's a new feature added in 4.5.0 - these custom attributes are not being sent to GUI client.

You may want to keep several comma-separated timestamps in one persistent storage entry or custom attribute. It's convenient to do this by converting comma-separated values to array and back, e.g.:
s = "123,456,789";

a = s->split(",");
println(a);

s = ArrayToString(a, ",");
println(s);

P.S. There's a trick to temporarily change polling interval for a node - you script can add custom attribute named
SysConfig:Objects.ConfigurationPollingInterval
with new value of polling interval. More info here: https://www.netxms.org/documentation/adminguide/concepts.html#polling

This can be accomplished by copying only one row to a temporary table:

create temp table saved as select * from config where var_name = 'DBConnectionPool.MaxLifetime' limit 1;

delete from config where var_name = 'DBConnectionPool.MaxLifetime';

insert into config select * from saved;

Ok, and if you connect to your DB using postgres tools and run
select * from config where var_name = 'DBConnectionPool.MaxLifetime';

how many lines this query will produce?