NetXMS Support Forum

If you have list of missing or poorly described topics I'll be happy to work on them.
It might be hard to notice them mostly developing the product(without real usage).

Hi,
Please check this forum discussion:
https://www.netxms.org/forum/general-support/custom-attributes-as-parameters-to-dcis/ - described how to get custom attribute as DCI parameter

Hi,

We are doing our best to organize documentation in next way:
- Admin guide - main documentation that will contain overall information about the system and detailed description of views and possible actions. Small amount of very simple examples. (Most of configuration parameters are already described in documentation: https://www.netxms.org/documentation/adminguide/appendix.html#agent-configuration-file-nxagentd-conf and https://www.netxms.org/documentation/adminguide/appendix.html#server-configuration-file-netxmsd-conf)
- Wiki - all "How to" and script/code examples, information for developers

Second level of debug. Messages should be something like: "%s: PDH Error %08X in call to %s (%s)"

Please check that option "Connect over slow link" is not selected(on the very first login screen). This option basically prevent MIB download to client, so explorer will not work.

We have not faced any issues with auto remove.
Please verify, that "Remove this template automatically when node no longer passes through filter" option is selected for the template on "Automatic Apply Rules" property page.

Also in your script:
Template will be applied to all routers with custom attribute or to bridges(with or without custom attributes). If you want to check custom attributes for bot is should look like:

if ((GetCustomAttribute($node, "RANCID_ENABLED") ~= "1") && (($node->isRouter ~= "1") || ($node->isBridge ~= "1")))
{ return true;
} else {
return false;
}

Do you use custom schedule together with "Agent cache mode"?
This combination will not work - it is known bug, that will be fixed some day: https://track.radensolutions.com/issue/NX-713

Please try second solution from this post: https://www.netxms.org/forum/general-support/%27invalid-netmask%27-for-node/

Да. Policy бывают теперь 2х видов - по факту это просто файлики которые при наложении передаються на агенты и складываються в папочку для дополнительных конфигов. Дальше уже сам агент знает что за тип конфига и спользует его соответствующе.
Про Agent Configuration Policy можно почитать тут: https://www.netxms.org/forum/general-support/agent-policies-vs-agent-configuration-files-on-server/ и тут https://www.netxms.org/documentation/adminguide/agent-management.html#agent-policies
Log Parser Policy это фалй который будет использоваться для парсинга логов. Для его использования необходимо настроить загрузку SubAgent = logwatch.nsm. Полько вместо создания и загрузки в ручную парсеров на систему можно это делать через Policy. Про лог парсер больше можно узнать тут: https://www.netxms.org/documentation/adminguide/log-monitoring.html

Hi,
It is possible to get last values for DCI using Rest API.
Rest API information: https://wiki.netxms.org/wiki/Web_service_API

URL for DCI last value history: /objects/{object-id}/datacollection/{dci-id}/values GET request with possible filters from=timeAsUnixTimestamp, to=timeAsUnixTimestamp,t imeInterval=time in seconsds, itemCount=numberOfItemsToReturn

Option to get last values for multiple nodes for the same DCI. AdHoc Table functionality through rest using custom defined table :
URL: http://10.5.3.4:8080/api/summaryTable/adHoc
POST request Json:
{
    "baseObject":"ContainerName",
    "columns": [
        {
        "columnName":"Name1",
        "dciName":"DCIName1"
        },
       {
        "columnName":"Name2",
        "dciName":"DCIName2"
        }
    ]
}

Hi you should add init.d scripts to your system. I have attached examples for centOS.

In those file you should set correctly:
$NETXMS_BINDIR
$NETXMS_LIBDIR
$NETXMSD_CONFIG
$NETXMSD_PID_FILE

Примерно так:
interfaces = GetNodeInterfaces($node);
foreach(i : interfaces)
{
   return i->macAddr like "85:55:*";
}
return false;

Функциональность доступна начиная с версии 2.1-М1. Ссылка на ошибку https://track.radensolutions.com/issue/NX-53

It should look like:


trace(3,$event->toJson());


For now only 2.0.x branch is considered as a stable one. All 2.1-Mx are Milestone releases before 2.1.0, which will be considered as a stable release.