NetXMS Support Forum

Какого-то удобного способа отображения нет. Можно сделать второй DCI, Origin Internal, в поле parameter "Dummy" и в трансформационном скрипте

offset = 60*60*24;
window = 120;

values = GetDCIValues($node, FindDCIByName($node, "DCI_PARAM"), time() - offset - window, time() - offset);
if (values->size > 0) {
  return values[0];
}
else
{
  abort;
}

Трансформационный скрипт будет искать DCI имеющий параметр DCI_PARAM, искать по нему значения собранные в интервале 24 часа 2 минуты назад - 24 часа назад и брать из этих значений последнее. Если оригинальный DCI собиратеся реже, чем раз в минуту, нужно увеличить window.

Ну и дальше по этим двум DCI строить график.

Попробуйте, плс, 3.8.226, вроде бы недавно были какие-то оптимизации с картами.
Что с загрузкой CPU на машине, где запущена консоль?

2. на этот счет есть план какое-то время сохранять недоступные узлы на карте. Создал issue чтоб разработчики не забыли: https://track.radensolutions.com/issue/NX-2030

It's being read by SNMP. No additional configuration should be necessary, if it can get something from a device via SNMP, it should be able to get topology data.
There is a separate type of polling called Topology poll. You can try briefly setting debug level to 6 on the sever and running topology poll for a node - in the log you should see what exactly it's reading from the device.

Hi!

Here's an example of such script:
global emails = "";

sub parseGroupsOrUsers(arr)
{
  for (i : arr)
  {
    if (i->isGroup)
    {
      parseGroupsOrUsers(i->members);
    }
    else
    {
      if (i->email != "")
      {
        if (emails != "") emails = emails . "; ";
        emails = emails . i->email;
      }
    }
  }
}

parseGroupsOrUsers($node -> responsibleUsers);
println(emails);

In NetXMS users groups can contain not only users, but also user groups, hence the script is recursive.

Here's a not-yet-documented way to print all attributes and values of responsible users/gropus:
for (r : $node->responsibleUsers)
{
  for(a : r->__class->attributes)
     println(a . " = " . r->__get(a));
  println;
}

The intended behavior of NetXMS is the following:
- on each configuration poll we are checking, if we can comminicate with the same community string, as before
- if we can not, then search sequence is started - first using snmp v3, then with v2c and 1 we try the community strings listen in Network credentials.
- If working snmp community is found, it's updated into properties of the node.

So it should be able to restore communication if community name is changed on the device.
Check if "Prevent automatic SNMP configuration changes" is not set in node properties.
Share output of configuration poll after community name change on a node.

It's advised to upgrade your system - current version is 3.8. There could have been changes since 3.5 that would fix this issue.

Would this behavior countinue in 3.8, try partially disabling DCIs to isolate ones that are causing the issue.

BTW, do you have any external parameters / providers where agent would be calling some other commands?

I will try to replicate this next week, no need for the issue for now. BTW, we don't use github tracker much, issues are tracked in track.radensolutions.com/

Currently on windows it's sending in encoding specified in control panel - language for non-unicode programs.

We plan to make configuration option that would turn on UTF-8 sending - progress can be tracked in this issue
https://track.radensolutions.com/issue/NX-2013

We plan to pack a JRE along with the console to simplify all this.

You mean when setting log file as syslog, right? (LogFile = {syslog})

Replicated that. It's related to interface loading optimization that was done a few versions ago - information about all interfaces is not being loaded on console start to make the startup faster.

В следующем релизе планируется паковать нужную версию JRE вместе с nxmc

The report engine used is Jasper Reports: https://en.wikipedia.org/wiki/JasperReports

An example of report could be found, e.g., in this forum message: https://www.netxms.org/forum/general-support/reporting-server-4315/msg20117/#msg20117

For Debuan/Ubuntu the best practice is to install and upgrade by means of OS package manager (apt / apt-get). There are tools to automate deployment of packages like Puppet, Chef, etc.

Installing using apt and upgrading from NetXMS Package Manager should not be done - location of binary/configuration/log file could be different and there'll be mess on the target system.

Попробуйте 3.8, она вышла только что