NetXMS Support Forum

Totally can be that editing this in some previous version caused the issue. So, let's treat it as working now.

Something as simple as
Action=debug:echo "$1" >> /tmp/a.txt
works for me with these letters. But I did not try in Docker, can you check if this works there?

Can you show your ping.sh script?

Can you point me to n8n documentation on the api call you are trying to use

I've checked your initial message, do not truly understand what is meant by "linked the agent to a container in a zone".
Agent should be specified in Zone's properties on Communications page. Zones are found under "Entire network" (Network perspective).
From agent's side it's configuration should have
EnableProxy = yes
EnableSNMPProxy = yes

If issue still persist, please grep the log for 2-3 specific IP addresses so that we have full process for each of them.

You can issue a token from Users and groups by right-clicking on a user.

It's one of the possible values for object's status (https://netxms.org/documentation/nxsl-latest/#const-object-status)

This script should do the job:

return $object.status == Status::UNMANAGED;

Where exactly you are checking for new nodes, under Infrastructure services or under Entire network?

You can enable debug, in server debug console:
debug poll.discovery 6

Then check server log, there should be some messages on what's happening.

To disable debug:
debug poll.discovery -1

nxget is not supposed to work with web services.

Do you have issues with configuring metrics from NetXMS server or what exactly you are trying to achieve?

Hello,

How many alarms do you have in NetXMS? You can do "sh st" command in server debug console to see the number. In 5.2 it worked that way that if Alarms tab was opened at some moment, it stayed in background and consumed resources. This will be fixed in 5.3

One recent finding is that Stacked line charts can lead to behavior like this - this is currently being fixed.

And you can check .nxmc4/nxmc.log file in your home folder for any errors

.apkg installer is actually a shell script joined with archive that contains agent file. If you do
head nxagent-5.2.6-linux-x86_64.apkg -n 118
you'll see the contents of the script.

I've tried to install it Ubuntu 24 Server, did not get the result that you are observing.

.apkg installer writes log file to /tmp/nxagentupdate.log. If you can repeat the installation, can you share that file?

Well, yes, FindAlarmByKey() is not searching through already terminated alarms, only current ones. And even if everything happens within one  EPP rule, alarm termination happens first and server action happens after that.

So the solution for now is to store the ID somehow before alarm termination. We can use filtering script in the EPP rule:

a = FindAlarmByKey($event.lastAlarmKey);
$event.setNamedParameter("lastAlarmID", a.id);
return true;
return true; is needed since this is filtering script and EPP rule will be processed further only if this script returns true.

And in your script that is used by the %[script] macro:
return $event.getParameter("lastAlarmID");

We are adding a new parameter to the event. This parameter will be accessible in any EPP rule that goes below the one where it's being added.

Ah, and actually you don't need the %[script] thing any more - you can just use %<lastAlarmID> macro - this should return value of event's parameter.

Currently it only writable by jira or redmine drivers, so only by developing a new driver.
But in overall it would be good to allow setting it from nxsl (because integration now can be done just with nxsl and web services). I've created ticket for that: https://track.radensolutions.com/issue/NX-2843

Well, while not being a LLM, I've hallucinated about $alarm . It does not actually exist.

But in $event there's lastAlarmKey attribute, so we can use that to get alarm's ID:

a = FindAlarmByKey($event.lastAlarmKey);
return a.id;

Or course, alarm should have a key and this key should be unique.

At some point we will add lastAlarmID attribute to $event.

At some point we will add built-in metric for systemd servicees (https://track.radensolutions.com/issue/NX-2841)

Currently this can be done by configuring ExternalMetric that would call systemctl show SERVICE_NAME --no-pager and pipe it to grep to get the status...
or you can try the new agent functionality that parses xml or json data provided by external commands. It's called external data provider, documented here: https://netxms.org/documentation/adminguide/agent-management.html#externaldataprovider

Add the following to agent configuration file:

### Data provider for systemd service information
[ExternalDataProvider/systemdServices]
Command = systemctl list-units --type service --full --all --output json --no-pager
Description = Data provider for systemctl json output
agent will now have systemdServices() metric that supports jq query as parameter and here's example of metric to get status of cron service:

systemdServices(".[]|select(.unit==""cron.service"")|.active")


Hi,

alarm message is defined in Configuration->Event templates. There in the message field you'd find something like %<{multipliers, units}currentValue> - multipliers define that value is converted to G, units would display measurement units if these are defined in DCIs properties. So setting just %<currentValue> would display seconds.
But you also can check history of the DCI - you'll see the values there. Or just Data Collection tab - you can turn multipliers on and off via context menu.

Also note that in 5.x there's built-in time synchronization functionality. If you call Status Poll manually, it will print time difference. If agent configuration parameter SyncTimeWithServer is set to yes, time will also be synchronized on status polls.