NetXMS Support Forum

Since this post was never answered, allow me to post some details:
Currently, SNMP and NetXMS Agent proxying is fully supported. Data (Traps, collected DCIs, etc.) will be cached if the connection to the NetXMS server is down, and when the connection to the server is restored, reconciliation will happen (meaning agent will sync data back to the server).
Proxying is supported for whole zones, as well as for individual nodes (or groups of nodes) if you are not doing zoning.

Syslog proxying is however currently not supported, but from what I know, its on the ToDo list.

As for what we use for local customer proxies, Raspberry Pi's are great for that.

Scheduled script is the functionality you are looking for.

1) make sure your user has access to the scheduler features (in user manager)
2) go to "Configuration > Scheduled Tasks"
3) create a new scheduled task
4) set type to "Execute.Script"
5) you can leave execution object empty, your script can then iterate all objects and execute on whichever you need
- this is of course limited by security policy as explained on this wiki page
- how to iterate over all nodes example on this wiki page
6) put the name of your script in the Script Library into the "Parameters" field
7) set cron schedule
- this is in standard cron format, if you dont know it, just google for "cron generator", for example this one

Ok, so after a bit of digging, Poller thread pool is not related to your issue.
The poller thread pool is used for all polls (topology, status, etc.).

NumberOfDataCollectors is the number of threads used for data collection.
There shouldnt be a need to increase it above 25 for an installation like yours.

What could cause this is too big agent/SNMP timeout combined with multiple DCIs timing out.

Other than that, I suggest going directly to Raden and opening a support ticket with them to resolve the issue, since its quite strange.
You can use the https://www.netxms.org/contact/ form.

In 'Server Configuration', what are your settings for:
'PollerThreadPoolBaseSize'
'PollerThreadPoolMaxSize'
'NumberOfDataCollectors'

How do the graphs for 'Server thread pool POLLERS' DCIs on the NetXMS server look like?

What version of NetXMS are you running?
How many nodes and how many DCIs in the system?

'Data collection poller's request queue for last minute' should always be pretty low, and should definitely not keep growing for longer periods.

1) Use 2.0.3, RC2 is quite old.
2) Use the Java Management console, not the legacy one.

Let us know if the problem persists after those changes.

It means that the new switches are not supported by the current CATALYST-GENERIC.

This means that Cisco changed something for this model in how the information which NetXMS needs is stored in the MIBs the device offers.

You can force a driver for a node by setting a custom attribute "snmp.driver" for that node to the desired driver.

No guarantee the driver will work tho, since the new switches might implement things differently it their MIBs.

You can use a "Data collection error" threshold.

Of course a data collection has no value and will not show in history, but you can still create a threshold that will generate an event when a data collection error occurs.
As I mentioned, its available as a Function in Threshold definition.

Go in an try it out.

Is creating a threshold on data collection error not enough?
This is available as a Function in Threshold definition.

From what I understand from your post, creating an event on data collection error should be enough for what you want to do.

Can you replicate the problem in a simple to use function?

Using this in "Execute server script" works fine for example:

sub test() {
  return %(1,2,3);
}

return test()[1];



Moving the function "test()" to a library script named "test_func" and then running this script also works fine:

use test_func;

return test()[1];


So it sounds like your problem is somewhere else.

I think you issue is insufficient memory assigned to Tomcat, thats why it works with dedicated client, but doesnt work with Web client.

See this topic for exactly the same issue:
https://www.netxms.org/forum/general-support/snmp-mib-explorer-crash-on-v2-0-m2/

Per-process memory usage is really easy, simply use NetXMS Agent's parameter

Process.WkSet("some_process.exe")


If you only have SNMP access, you can use this:
https://wiki.netxms.org/wiki/OS_process_monitoring_using_SNMP

As for monitoring CPU usage of individual processes - I personally dont know any way how to do that.

If the switches provide topological information (LLDP, STP MIB, etc.), NetXMS will automatically correlate event, and create an alarm only for the source event generating the outage.

What version NetXMS are you running?

Are you using beta or main apt repo?