NetXMS Support Forum

Поправим в следующем релизе, пока что попробуйте скачать https://netxms.org/download/releases/3.5/nxmc-3.5.90.war и положить его в  C:\NetXMS\WebUI\nxmc\nxmc.war

Hi!

There is an option called tunnel, when agents are establishing connection to NetXMS server. Connections are performed to port 4703 (configurable in server configuration parameters), so you need to open this port on the router where your server is running.

Configuration is a bit tricky - you need to create security certificates, just follow the sequence in the documentation:
https://www.netxms.org/documentation/adminguide/server-management.html?highlight=tunnel#server-configuration-for-agent-to-server-connection-tunnel-connection

Сделали изменения, в 3.5. должны поддерживать русские имена баз и пользователей.

Please share log of management console - it's located in user's home folder in .nxmc/data/.metadata/.log

У этих DCI поменялись ключи, сейчас там, например, Server.QueueSize.Max(DBWriter.Other). Эти изменения есть в новой версии темплейта, но автоматом мы не перезаписываем темплейты, чтоб не потерять изменения, которые мог cделать пользователь.

Что можно сделать:
а) Поменять конфигурационный параметр сервера ImportConfigurationOnStartup на Always, перезапустить сервер. Сервер при старте перезапишет темплейты.

б) Вручну импортировать новый темплейт, поставив галочку "Replace existing templates", через Tools->Import Configuration. Он лежит в C:\NetXMS\share\templates\netxms_server.xml

Yes, you can use createdBefore, createdAfter, updatedBefore, updatedAfter. Unix timestamp should be provided to these filters.

Also, you can filter by alarm state, e.g.
alarm=outstanding
or
alarm=outstanding,acknowledged

And there's a good thing resolveReferences=true, in this case you'll have names of all related objects in the json output.

There are also filters by user name, you can check in sources for these: src/client/nxapisrv/java/src/main/java/org/netxms/websvc/handlers/Alarms.java

Hi!

The way you tried is not yet implemented. What works is this way:

/alarms?objectId=123

/alarms?objectGuid=XXX

If you need to see alarms for all nodes under a container:
/alarms?objectId=123&includeChildObjects=true

Выложили

Should be available now

Memory leak has been fixed. It will be included in next release.

It should be possible to run without administrative rights. Communication of user support application happens through main agent process. So it's necessary to start agent process as well.
This could be done by some sort of bat file, so you can try packing all this into self extracting archive or something.
Current issue will be that agent process will produce a console window while it's running. It could be possible to add hiding of it's window is some of future releases.
You can try experimenting with all this - may be there will be some other issues on that way.

Created https://track.radensolutions.com/issue/NX-1945 for the memory leak.

Auto-refresh was implemented as a quick fix to get desktop video.
The proper way is, certainly, live video stream with some suitable codec, but this requires developer's time which is always busy with something.

Tags were reworked in 3.x - was added ability to have multiple tags for event. %u was deprecated. Currently you can use %[script_name] macro and make a script that will go through tags and return the value.
Created an issue https://track.radensolutions.com/issue/NX-1944 to make a macro that would return tags in concatenated form.

This should have been fixed in 3.4.318 of management console. Please try upgrading if you are on lower version.

It's a bug. Created https://track.radensolutions.com/issue/NX-1943 for that.

This is how the integration was designed - currently it's not possible to close alarm while helpdesk ticket is open.