NetXMS Support Forum

Table functionality predates instance discovery. It was first attempt at handling multi-instance data, and it turns out to be quite complex in configuration and storage. Then instance discovery was added, and in my opinion it is much better approach for collecting multi-instance data, with tables have only limited use. Tables could be used when data really needs to be processed as a table - when you need to combine data from multiple columns and multiple rows (instances) for example. They also could be easier way to present multi-instance data on dashboards.

Best regards,
Victor

Do you really need a table or you can replace it with instance discovery? If yes then you can just set usual threshold on DCIs.

Best regards,
Victor

You have to create it by running reconf script if you clone GIT repository. Or just use source package that I've provided in the post.

Best regards,
Victor

Just fixed it, commit 368c35ad0d in branch stable-3.8.

Best regards,
Victor

P.S. Download link to new source package for convenience: https://cloud.radensolutions.com/s/JCLQKsm3c8YSYSJ

If you have it a s a node in NetXMS, then server will generate usual SYS_NODE_UP event. All you have to do is to create rule which somehow will filter SYS_NODE_UP eents only for such nodes. It could be filter script that check container membership or certain custom attribute.

Best regards,
Victor

Hi,

changing color of the link is also possible if it has DCIs associated - then you can select option "include active thresholds into calculation" in link properties and it will change color if there is active threshold on one of associated DCIs. Side effect is that values of those DCIs will be displayed on the link as well.

Best regards,
Victor

And what is actual file size?

Hi,

try to run file transfer manually from server with nxupload command line tool - when will it stop and with what error? If possible, capture TCP session between server and agent used for upload and provide capture file.

Best regards,
Victor

Hi all!

We just published another patch release for version 3.8. Changes since previous patch release:

- Database manager can detect and delete orphaned data tables
- Event processing macro %A (alarm message) also works in rules following one that triggered alarm as well as when alarm is resolved or terminated by the rule
- Fixed agent crash on log parser rule with inverted match
- MIB compiler accepts object identifiers that starts with uppercase letter
- Implemented hash map to string conversion in NXSL
- Fixed save of node state
- Web API included into Web UI installer on Windows
- Fixed deployment issues with Web UI installer on Windows
- Fixed issues:
        NX-227 (Create "nxdownload" utility)
        NX-553 (CPU and Memory DCI support in Darwin)
        NX-1006 (Node with all status poll sources disabled creates a down alarm)
        NX-1057 (Ability to execute set of SQL commands on server start)
        NX-1473 (System Description for Agents that are also running SNMP should be Agent's description, not SNMP's)
        NX-1851 (nxdbmgr not checking for situation when DCI present in items, but not in object_properties)
        NX-1882 (Add option for negative mask in File.Count, File.FolderCount, and File.Size)
        NX-1947 (Server repeats SYS_IF_DOWN after SYS_NODE_UP even if interface was already down before SYS_NODE_DOWN)
        NX-1976 (Add interface names to automatically generated IP topology maps)
        NX-2043 (Delete "last agent contact" timestamp when isAgent capability switches off)

Best regards,
Victor

It's probably good idea to grant write access to whole \NetXMS\var - service may write other files there as well (most likely \NetXMS\var\images if you will add custom object images).

Best regards,
Victor

Hi!

Try to add the following option to netxmsd.conf:

DBCacheConfigurationTables = no

Best regards,
Victor

Повторил у себя. Похоже по умолчанию в агенте слишком маленький таймаут на выполнение внешних процессов. Добавил в конфиг

ExecTimeout = 30000

и рестарт сервисов заработал.

Скорее всего у текущего пользователя нет прав на шаблоны. Попробуйте зайти пользователем system, у него всегда есть все права, и проверьте права доступа в свойствах объекта Templates.

Hi,

the tricky part is what to consider uptime. If purely time when node was unreachable (like 100 - (intervals between SYS_NODE_DOWN and SYS_NODE_UP) / period length) then it is quite simple. In fact it can be done on current version with reporting. If uptime should include more conditions, like that all services are running on the node, then it became more complicated. This is what business services were meant for, but they are very hard to configure and definitely need rework.

Best regards,
Victor

Save the date – April 29, 2021 at 5pm CET (11am EST).

We will organize online Q&A session with NetXMS developers. Please contact @moshenska in our Telegram support channel or at [email protected] to sign up.