NetXMS Support Forum

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.

Is it possible to set the helpdesk Ref on an alarm via the API? if not what table/column can i update in the dB to set it?

Hi Filipp

thanks for the assistance that works great for new alarms unfortunately when it runs for a terminating alarm it doesn't return the alarm id

Regards
Richard

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,

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. 

Hi,

I need to monitor current time with NetXMS server for all workstations with NetXMS agent installed on them. The idea was to compare the current system time (macro %T) on the NetXMS server with the data obtained from the NetXMS agent System.CurrentTime. Unfortunately, after the first poll query I received an alert that the limit set in the threshold rule was exceeded with the content "Threshold reached for data collection item "Current system time" (Metric: System.CurrentTime; Threshold value: 1.76 G; Actual value: 1.76 G)". From this message I cannot see exactly which timestamp was read because it is expressed in giga format. Does anyone have an idea how to perform a system time check on nodes with server time and trigger an alarm in case of a mismatch.

Thanks in advance
Tomislav

Hi Team,

Is there any plans to add more features to the Network Discovery option in NetXMS Server and Proxies? We are keen on getting these features in line with nmap's discoveries added to Network Discovery -

• Port Scan
• Service/Version Detection
• OS Detection

Regards,
Mathew

Quote from: tolimanjo on September 30, 2025, 05:41:40 AMI was getting the '500' error from the client when using HTTP, and a packet capture showed HTTPS style connection attempts to the server. Perhaps Android was trying to be helpful?
Anyway, putting an HTTPS-HTTP proxy in front of the server (and specifying https:// on the client) fixed the problem.

if protocol is not specified in the connection string, https:// is added.

Добрый,

на сейчас агент не умеет работать с регистром напрямую, можно настроить ExternalMetric в конфиге агента, которая будет вызывать regedit. Вероятно можно и ExternalList чтоб получить список ключей в ветке регистра, но не знаю насколько удобно парсить выдачу regedit для этого.

Тикет на прямую работу с реестром есть, когда-нибудь будет сделано
https://track.radensolutions.com/issue/NX-2838