NetXMS Support Forum

Добрый,

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

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

nxdbmgr convert - это именно in-place конвертация, без создания второй базы.

Yes, right, these are the macros described here: https://netxms.org/documentation/adminguide/event-processing.html#macros-for-event-processing

There's no built-in macro for alarm ID, but there's %[script_name] which will call a script from script library. There'll be a few variables set in the script, specifically:
$object - always is set
$node - set if event is created on a node
$event - when script is called from EPP
$alarm - if at given moment of event processing by EPP rules an alarm is already created.

$alarm variable has Alarm class described here: https://netxms.org/documentation/nxsl-latest/#class-alarm , so simple script

return $alarm.id;

should do the job.

Can you capture network traffic on server's 8000 port using tcpdump (tcpdump -s 0 -w snmp.pcap port 8000) or Wireshark if you are on Windows.
You can send resulting file to me via private message.

Also check netxmsd log, may be there are some error messages there.

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.

You can create four nodes enabling "Communication through external gateway" checkbox on them (actually, on three of them, so one of them will be treated as main node and NetXMS will read network topology for it).
For each node you can now set specific port.
If you want all DCIs on one node, you can use Source Node Override in DCI properties.

The syntax is URL-like
http://hostname:port or http://IP:port

It's adviced to put e.g. nginx as reverse proxy to add ssl (then url would obviously by https://), but if you use VPN you are good with just http

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.

Just tried a fresh install on Win 10, HTTP / HTTPS buttons work from a dashboard. But other elements of dashboard could affect things.
Do you have any error messages in C:\Users\<Your username>\.nxmc4\nxmc.log when you try to use these dashboard buttons?

Hi,

git-enabled configuration might be nice, but then comes a question what should be included like templates and other stuff, so this may end up in serious development effort and the resources are limited.

What can be done currently - there's nxshell api that allows to do everything that management client can do. So you can import and export script library scripts (and get list which scripts are in the system).

Yes, it takes some effort to renew them and there's always no time for that. Which images are most problematic, you can just post image URLs from web version of docs or name of chapter.

Hi,

Can you add
DebugLevel = 6
to agent's log and collect the log for the period of time while package upgrade is happening?
You can share the log file via private message if needed.

The thing that I forgot to mention - in Configuration->Server configuration there's parameter named Server.ImportConfigurationOnStartup. Setting it to Always and restarting the server will revert built-in templates to their current versions (they are stored in /usr/share/netxms/templates/ on the server).

Setting "Only missing" has same meaning as not selecting "Replace templates" in the manual import - if given template (they are identified by GUIDs) is already present in the system, no changes will be made to it.
So if you have "Only missing" setting, delete a template and restart NetXMS - template will reappear (but all historical data on nodes will be gone).

IOS client is published to the App Store. It's still beta, so some things may not work properly.

It needs new API that is built in into NetXMS server. Latest server version is recommended, not that for Postgres users it's not recommended to upgrade to 5.2.5 as there's an issue there, pls wait till 5.2.6.

Quick setup guide:
- add "Module=webapi" to netxmsd.conf, module listens on port 8000 by default. You can change it:
[WEBAPI]
ListenerPort=12345

Please note, it's unencrypted HTTP!
- add nginx, reproxy, traefic - or any other ssl offloading app in front of it.
- connect to the API endpoint.

The progress bar above the buttons in this dialog should get filled with blue when the file got uploaded, then OK button would become active. This means that you have some issue with browser not uploading the file. Check security settings, may be try another browser or you can try the Desktop Client.