NetXMS Support Forum

Да, повторили, будет чинится в этом тикете: https://track.radensolutions.com/issue/NX-2929

It uses GLOB matching, so supports * and ? wildcards. What NetXMS version you are using, is it web or desktop UI?

Just published 6.0.3 - it should have the fix.

Today we have published patch release 3 for version 6.0. Changes since previous release:

- Added wireless controller bridge for Aruba Instant controllers (PR #257)
- Improved interactive SSH mode support
- Improved web API
- Windows agent renames in-use files during upload if they cannot be replaced
- Fixed incorrect handling of empty tool call list in LLM response
- Fixed bug in database schema upgrade on Microsoft SQL Server
- Fixed issues:
   - NX-2369 (Option to add number of items in a container)
   - NX-2867 (Disable "Create database and database user before initialization" if SQLite selected in Windows installer)
   - NX-2922 (New agent actions: enable / disable ExternalMetricProvider)

Just a quick update on this. I'm currently using MikroTik devices, and I can see the physical interfaces in NetXMS without any issues.

Physical interfaces are working correctly; however, virtual interfaces such as VLANs, PPPoE interfaces, VPN interfaces, etc., are not appearing.

Could you please advise what might be causing this or what I should check to ensure these interfaces are discovered properly?

Filip

about Create Data Collection Items:
this is what im doing:

Navigate to Infrastructure Services in the object tree.
Right-click on Infrastructure Services and select Properties.
Go to the Custom Attributes tab.
ADD:
Name: Template.InterfaceTraffic
Value: YES
tick the "Inheritable" box.

Pull->configuration

is not working

can you pleas advice

Wow, that's awesome, thank you so much!

I've found the issue. When no tool calls needed, your model returns tool_calls as empty array, but server code only checks for missing or null tool_calls. Just fixed that, upcoming patch release should work as expected.

Quote from: johnnyva on February 23, 2026, 11:42:37 PMHey Victor will the change in idata/tdata timestamp to millisecond impact the REST API or NXSL dci values? i.e. will we see millisecond timestamp there as well or will we only see change in db?

New REST API (webapi module) - it is using ISO 8601 format for timestamps which allows milliseconds (although 5.x did not set millisecond part), any decent ISO 8601 parser should handle milliseconds correctly.
Old REST API (Java app) - should be unaffected.
NXSL - all timestamps for collected data are now in milliseconds.

Best regards,
Victor

Thank you for the update.  Any ETA when the console, agent, etc will have a patched openssl (CVE-2025-15467).

Thanks in advance!