Found the issue, docker ran with POSIX had to add ENV LANG=C.UTF-8 ENV LC_ALL=C.UTF-8 Now it works with åäö

also you don't need "function main()", just write code. something like this: source = FindObject($alarm.sourceObject()); j = JsonObject(); j.set("id", $alarm.id); j.set("state", $alarm.state); j.set("severity", $alarm.severity); j.set("message", $alarm.message); j.set("source", source ? source.name : ""); j.set("eventCode", $alarm.eventCode); j.set("eventName", $alarm.eventName); trace(0, j.serialize()); I highly recommend you to read https://www.netxms.org/documentation/nxsl-latest/.

Perfect !! Thank you

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

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")

Thank you Filip, I will try to adjust DCI current measure with to see exact value of timestamp. I hope that will be resolve this issue. Also I will try built-in time synchronization functionality.   Tomislav

Hi Filipp, Thank you for your support. The "Communication through external gateway" checkbox solution works perfect. BR, Zsolt

Thanks, that's was exactly what I needed.

The thing is that on some Linux Distros only Maria DB is available. That's why Alex recommended to put DBDriver=mariadb into agent's configuration file instead of DBDriver=mysql You've achieved the same result by copying database driver file, but this is not correct approach, because on next upgrade you'll get new version of mariadb.ddr file and if you forget to copy it, you'll get strange errors.

Oh nice, thank you. Maybe you can add this to the manual for future reference!

I'd suggest to experiment a bit - you can make a new template with just one DCI and see what happens when you export or import that. For duplicates - it's controlled by GUID of each template that is included in the .xml file. So if you import it back, it will replace the original template, even if the name is different. But if you change the GUIDs in the .xml, it will import as a new one. Only "Replace templates" option is relevant if your .xml contains only templates. If it's not checked, then if template already exists, no changes will be done to it.

No problem Filipp.  Appreciate the response.  You're correct; I have multiple hierarchies so nodes exist in multiple places (i.e. it might be listed in my physical topology under "Core Routers" but then it might also be listed under Manufacturers > MikroTik... I think this is just for my visual benefit / sorting more than anything else.  I know I tend to over-complicate everything haha).  Thanks again, and look forward to the fix (noting that B would be my preference, so we don't ever delete a bunch of custom attribute values...like keys/passwords/etc that could be impossible to recover or recreate easily).  ~C

Thanks Filipp, you are of course right.  It was after a recent server restart, and after a configuration poll, it is now showing up. Cheers.

Yeah the problem was that NetXMS shows both local config seting and config policy applied via template, after editing local config and restarting agent everything is ok. Thx for the effort anyway.

Ok, changed the code, thx again for the info

Yes, we work with StarWind since 2017. Best regards, Victor