NetXMS Support Forum

In 4.2 support for TCP proxying was added into agent and desktop management client (and was not yet documented)

Agent should have EnableTCPProxy=yes in it's config

In management client it's done via Object Tools, there's "Setup TCP tunnel..." checkbox.
There are two macros - ${local-address} and ${local-port} which are replaced by actual local IP and port

So Local Command object tool with command
mstsc /v:${local-address}:${local-port}
should work for RDP

What exactly version of NetXMS do you have?
Could it be that your NetXMS got upgraded recently?

If you have that node under some other container or template, you can remove it from cluster and then you can add it to another cluster (all done from cluster context menu).

By the way, how many clusters do you have in your system (just to understand the scale how people use clusters)

Добавили еще обработку сетевых ошибок в драйвере Телеграмма, это пойдет в 4.3

Something like this may happen right after server start, if you are taking values from a DCI that has quite frequent collection interval. In this case server is not getting last collected value from database, but awaits it from agent.
You can check if GetDCIRawValue returns null and handle this situation in the script.

You can make script DCI and process errors inside the script, e.g.:

s = $node->readAgentParameter("File.Size(/tmp/1/1.txt)");
if (s != NULL) return 1; else return 0;
s != NULL condition can be actually simplified:
s = $node->readAgentParameter("File.Size(/tmp/1/1.txt)");
if (s) return 1; else return 0;

I've used File.Size, as it is simpler and has just one parameter, but you can use File.Count as well.

P.S. Instead of script DCI you can use internal DCI with metric "Dummy" and have all the scripting in transformation script.

This could be done using filtering script in EPP. That script should keep last 10 timestamps somewhere (in persistent storage or in custom attribute of the node, as comma-separated list) and check if all these timestamps fit within 5 min interval.
Do you need an example of such script?

Great, thanks for the update. Documentation is now updated.

Just to note - PollerTrace line is optional - it just produces debug output when configuration poll is executed manually.

Looking at /src/ncdrivers/mqtt/mqtt.cpp, the following parameters should be in channel congit:

/MQTT/Hostname
/MQTT/Port
/MQTT/Login
/MQTT/Password



When sending, recipient becomes the topic and message body becomes the value.


Pls update, if this works for you

That's a moment when the scripting kicks in. Simplest is in HOOK::CreateInterface script - it's being called when creating a new interface. E.g. (for Mikrotik, adjust the OID for Unifi AP):

if ($node->snmpOID == ".1.3.6.1.4.1.14988.1") {
  PollerTrace("  Setting " . $1->name . " expected state to ignore"); 
  $1->setExpectedState("IGNORE");
}
return true;
If you return false from the script, the interface won't be created at all.

But for this to work you'd need to delete all interfaces for already created nodes. Alternative approach is to make a script that will loop through all nodes and their interfaces and set expected state - give a note if you need example of such script.

It's just display issue, should get fixed in next patch release

It's a bug. It was fixed, will be included in next patch release. If you are on windows, you can try this build: https://cloud.radensolutions.com/s/RMzPpdTMBGSmjQe

Also opening summary table configuration, clicking "Apply and Close" may help while management client remains open.

Looks like it's a bug. Created issue for that, you can monitor resolutions process here: https://track.radensolutions.com/issue/NX-2321

It's a bug introduced in 4.2. It affects syslog and windows event log processing in fields "source" and "tag".

Bug is fixed, will be in next patch release. 

Meanwhile you can put * character in syslog tag field, it should work that way.