NetXMS Support Forum

We will add displaying of IP address in list of sessions in a future version.
Currently you can set debug to level 5. This could be done on the fly in Tools->Server Console
debug 5

The messages that we want to see are these:
2022.04.13 13:10:01.442 *D* [                   ] SocketListener/Clients: Incoming connection from 127.0.0.1
2022.04.13 13:10:01.442 *D* [                   ] SocketListener/Clients: Connection from 127.0.0.1 accepted

so you can grep your server log by "SocketListener/Clients"

This way we will see from where these connections are coming.
Do you have any other integrations besides Grafana (nxshell, WEB API)?

Yes, on Windows in Task Manager on Details tab you can create dump file. The dump may have some sensitive information, so do not share it publicly.

This is actually strange. The only possible reason I can think of is if runtime error happens in the script. In this case script is interpreted as if it would return true (this will be reworked in next release). But script run-time error would be visible in the log file. And your script looks to be correct.

I would increase active discovery interval to 3600 - this is to make sure that discovery processes would stop. Then try setting server debug level to 6 (hopefully it's a test environment with not too many nodes - otherwise there will be too many lines in the log). And try to run discovery scan manually - select the range and click scan. The log should have detailed information on how discovery is happening.

I'd suggest to turn off the active discovery. Then to check that discovery queue is empty (run "show queues" from Tools->Server console). After that try deleting the nodes again and retry the discovery.

Hi!

I've added a couple of issues for these features:
https://track.radensolutions.com/issue/NX-2248
https://track.radensolutions.com/issue/NX-2249

NX-2249 is probably lower in priority, but might be done at some point.
Dashboard generation from performance tab is technically possible, but there's a lot of higher-priority things.

Hi!

Could it be so that nodes for these IP addresses are already present in the system when discovery happens? If so, the script is not executed, if that address is already added.

This was fixed in development branch and will be included in next patch release.

Не, простых путей нет

Все так и должно быть. Механизм репортинга - это лишь интеграция с Jasper Reports. А для Jasper Reports нужны .jar файлы с описанием отчетов, там есть какая-то Jasper Studio в которой можно эти .jar файлы создавать.

There was a bug that access rights for editing two-factor auth methods were not automatically added to admin users when this feature was introduced. Check access right for Admins groups in user manager.

1) Для начала нужно как-то собирать это значение. Например, сделаем DCI, Origin "Internal", Parameter "Dummy". А в трансформационном скрипте этого DCI сделаем все что нужно (то же самое можно было сделать с помощью DCI c origin "script"):

list = $node->readAgentList("System.ActiveUserSessions");
currentlyLoggedUser = SplitString(list[0], "\"")[1];
$node->setCustomAttribute("currentlyLoggedUser", currentlyLoggedUser);
return currentlyLoggedUser;


Для простоты скрипт сохраняет имя юзера в custom attribute на ноде - поэтому историю этого DCI можно даже не хранить.
И теперь можно пользоваться макросом %{currentlyLoggedUser} - там будет имя юзера.


Альтернативный путь - макрос %[script_name] и в этом скрипте можно находить нужный DCI и брать его последнее значение.

2) Репортинг на windows ставится инсталлятором сервера, там есть отдельная галочка.

It was finally documented

https://www.netxms.org/documentation/adminguide/user-management.html#two-factor-authentication

1) А о каких, например, событиях идет речь? Просто большинство событий никак не связано с тем, залогинен ли кто-нибудь в NetXMS. Может быть, что в данный момент вообще никто не залогинен, может быть что залогинено несколько юзеров.

2) В Services в Windows должен быть сервис NetXMS Reporting Server. Как он себя чувствует, стартует ли? Ему для работы нужна Java, 11 версии или старше.

some URLs were renamed to lowercase-style, please try API_HOME/summary-table/ad-hoc

Admin documentation should have this updated: https://netxms.org/documentation/netxms-admin.pdf

They will appear in upper left corner.