NetXMS Support Forum

Ok, so most of the requests ended up with timeout. But there's one thing that makes all this a bit complicated. When server talks to the agent there's timeout for this process. By default it is 4 seconds. But these network service checks have timeout of 5 seconds by default, which results in <<ERROR>>.
We've just changed the default timeout for web service checks to 1 second, this will be included in next patch release. Meanwhile you can specify the timeout in the metric, e.g.:

NetworkService.Status(https://mail.customer-mailserver.de, timeout=1000)

Right, favicon is not yet implemented in the new web ui. I've created a ticket for that, you can follow it to know when it's resolved: https://track.radensolutions.com/issue/NX-2777

Hi,

I am not sure about ServiceCheck.HTTPS metric as I do not see it in current docs, may be it's something from earlier versions.
Currently available metrics with some examples are available here: https://www.netxms.org/documentation/adminguide/service-monitoring.html#network-service-monitoring-using-dci

Note that netsvc subagent should be enabled in configuration file of the agent that you use to collect these metrics.

If you face <<ERROR>> you can set DebugLevel=6 in configuration file of the agent. Agent restart is needed for it to have effect. Agent log should have more detailed info about the reasons for the error. Feel free to share your log here

Documentation has an example of how to configure delayed notification and notification when node is back up: https://netxms.org/documentation/adminguide/event-processing.html#actions

Using a DCI for ICMP packet loss can be a way, but it does not cover situations when icmp is not working, but node is still accessible via SNMP or via NetXMS Agent

Great, thanks for the update

NetXMS is running node status poll every minute. If node stops responding SYS_NODE_DOWN event should be generated (the other option is SYS_NODE_UNREACHABLE - if NetXMS detects that loss of communication is due to some other node). So if you need notifications, notification actions in EPP should be configured for these events.

You can check Event Log on a node to see what events were actually generated.

Pls try this version of management client
https://cloud.radensolutions.com/s/ckxq7QQGPqDMzYH

Хм, а что дальше этот экшн делает?
Если что, тут есть пример создания нод через nxshell: https://www.netxms.org/forum/general-support/difficulty-using-the-csv-importer/

It's probably taking the first line of the output that was obtained via ssh. In this case it's !!!!!, which might be interpreted as 0 if the DCI is Integer.
If you check history for this DCI, raw value column might have some clue.

if your router supports i command which allows to filter the output, you can do something like this:
ping 8.8.8.8 repeat 3 timeout 1 | i SuccessThis would limit the output just to one line, which then can be parsed using transformation script. Note that I limited number of requests and timeout as by default there's 4 second limitation between netxms server and agent - result should be returned within that time.

If above is not possible, the other approach is to call ssh command from NXSL script. In this case all lines of output are received (as array) and we can parse this array to extract data:
r = $node.executeSSHCommand("ping 8.8.8.8 repeat 3 timeout 1");
avg = -1;
for (s : r) {
  m = s match "Success rate is .* round-trip min/avg/max = .*/(.*)/.*";
  if (m) avg = m[1];
}
return avg;

You can either put this script into script library and use it in Script DCI; or you can make Internal DCI with metric Dummy and put this into transformation script.

This query should list EPP rules that have actions. In the "active" column you should have 1 for active actions and 0 for inactive, but may be you'll get some other values.
select p.comments, a.action_id, a.active from POLICY_ACTION_LIST a INNER JOIN event_policy p ON a.rule_id = p.rule_id;
A query to activate them all should be just this:
update policy_action_list set active = 1;
Note that netxms server should be stopped before running any update queries to the DB.

Yes, pls try disabling and reenabling the actions. If this does not help, we will check how to fix them with a database query.

If you could provide us with access to some test aruba device for a few days, that would be the most efficient way for our developers. You can set up some vpn or just netxms agent with SNMP proxy enabled to which we could connect. If that's not possible, pls send full snmp walk output.

We've fixed a bug in import - when importing from older version of xml state of Action (active or not) was not correctly imported. The fix will be included in next release.

In overall it's better to upgrade just with the same database - new server will upgrade it's structure. Installing a new system and migrating config approach is used not so often, while perfectly valid.

Can you also select this from the DB and show the output (IDs are less by 1 then what's visible in the UI):

select rule_id, flags, comments from event_policy where rule_id in (59, 78);

Can you share the exported .xml (or at least it's part related to this specific rule).
Export was performed in v 2.2, right?