NetXMS Support Forum

This could be done with transformation scripts on a number of SNMP DCIs, but this is not convenient to manage, as transformation script on each of these DCis would be different. 

A cleaner approach would be to use script DCIs. In script library create a script, named e.g. getPduMetric with the following contents:

function main(oid, name) {
  transport = $node->createSNMPTransport();
  if (transport == null) return null;
  v = transport->getValue(oid);

  h = %{};
  for (a : v->split(",")) {
    b = a->split("=");
    if (b->size == 2) h[b] = b[1];
  }

  return h[name];
}
Then create a DCI on the node, origin should be Script. In the metric field we have name of the script with it's parameters:
getPduMetric(.1.3.6.1.2.1.1.1.0, activePower)

Script accepts two parameters - OID and variable name. This way you can have just one script and define everything in metric of your DCIs.

Sure, here's a couple of screenshots. First is log parser policy, file name is *Security which means that it's reading Security windows event log. It's picking only records with ID = 4624. Matching regular expression is .*, we can also use capture groups here, at maximum we can just put (.*), but this will pick the whole multi-line event description. Capture groups, if any, will also go as NetXMS event parameters.

On second screenshot we have event template. Message field describes which event parameters we use to compose the message - it's better to use parameter names instead of %1, %2, as number of parameters may change, e.g. if we add a new capture group, but names will stay the same.

Remember, that you need to apply the template to a node for this to start working.

Try increasing debug level for tag "ldap" by issuing

debug ldap 8

in server debug console (Tools -> Server Debug Console or nxamd -i from command line).
Then issue

ldapsync

command there - it will force the synchronization and check netxmsd log (/var/log/netxmsd)

Ok, so that explains.
If you can provide access to a test device, that would be great (but we would have someone who can work with it after 17-th of March). If providing access is not possible, then we would ask to perform walk for some OID branches.

that means that NetXMS server cannot read LLDP information via standard MIB. Server checks the following OIDs to test if LLDP MIN is supported by device:
1.0.8802.1.1.2.1.3.2.0
1.0.8802.1.1.2.1.3.6.0
1.3.111.2.802.1.1.13.1.3.2.0
You can check with any SNMP walk tool if device responds on any of those OIDs
Also, if you can provide SNMP access to test device, we can test it ourselves adn update server as necessary

It looks that there are problems with the dark theme in the framework that we are using: https://github.com/eclipse-platform/eclipse.platform.ui/issues/246

We will try to add some work-around, but this will take some time.

А какие на системе версии пакетов libcurl и libcurl-devel?

In my example event was generated by Event Log Parser on agent, by adding a Log Parser Policy. In case of Win Event Sync there's less information available.

Quote from: augusteDOUAMBA on March 06, 2024, 07:05:06 PMHello, I tried netxms on 500 node. It is a very powerful tool. Thank you and congratulations. I would like to deploy it on a wider scale. I don't have any planning tools on hand. Can the single server monitor 5000 nodes with 50000 dci?
If so, what should the characteristics of the server be?

Rough requirements are the same as mentioned above, 8-16GB RAM and 4 CPU cores, fast storage - ssd or nvme is recommended.
Attention should be paid to tuning of your database

Many of notification channel drivers depend on libcurl (and email sending was reworked to use libcurl somewhere in 4.x). How do you install the server, do you compile it yourself?

You can make a DCI with one of the following metrics: https://www.netxms.org/documentation/adminguide/service-monitoring.html#network-service-monitoring-using-dci

The DCI should be on a node that has agent running, e.g. on your NetXMS server node. But there's a way to overcome this - you can have this DCI on the node that you are monitoring and in properties of that DCI you can select another node in "Source node override" field.

In this case You'd need to create a Zone and set this worksation, which is on the same network as Synology NAS as proxy for that zone.

Could be firewall issue, some limits on server that prevent process from accepting connections. It was some time ago, so I hope it's resolved. If not, what's the output of
netstat -lptun
on your server?

Policy will be applied only to nodes, to which the template is applied (but should work in any sequence - either template was applied first and then policy was added, or otherwise).

On Windows systems default location for configuration policy files is
C:\Windows\System32\config\systemprofile\AppData\Local\nxagentd\config_ap
so you can watch this folder to check if policy gets there. Agent restart is needed so it can catch up the new configuration.


Also, on a side node, there are two ways how to monitor Windows Event logs - one is Windows Event Sync, when logs are sent to NetXMS server and stored there (so it requires bandwidth and DB space. The other is Log File Parser Policy - you can specify Windows Event Logs there in file name field, e.g. *Security

On your screenshot it's Event Monitor (which is updated in real-time). If you find this event in Event Log and double-click on it, you should have something like this: