NetXMS Forum

Sorry, this was overlooked for a while. First guess is that there are some issues with syncer thread. It's not visible in show threads, as there's just one syncer threads. In debug console there's netxmsd: sh sy Last run at .........: 16.Apr.2026 15:22:58 Last run time .......: 1 ms Average run time ....: 119 ms Max run time ........: 132 ms Min run time ........: 0 ms And System -> NetXMS Server -> Server Performance has metrics for it, specifically Server.SyncerRunTime.Last. Pls check if this metric looks reasonable. Slow log opening might indicate problems with DB performance, DB might need tuning. What are the specs on DB VM, is it dedicated to NetXMS or a shared database? How's CPU consumption and IO stats? How big is the database on disk? You can also use mysql subagent to collect stats about DB operation - https://netxms.org/documentation/adminguide/database-monitoring.html#mysql

Audit log is retained after node deletion, same for syslog. For event log there's Events.DeleteEventsOfDeletedObject setting in Configuration->Server Configuration, if set to true (default), they are deleted. And there's similar setting for alarms - Alarms.DeleteAlarmsOfDeletedObject. DCI data is deleted. If database is Postgres Timescale, then event log and DCI history is not deleted. In all above situations when data is not deleted, it would be problematic to view it since you need to know node's ID. New decommissioning functionality is basically node unmanage with addition of automatic deletion at later time. So for now you can just unmanage your nodes.

Hi,  Quite a few things changes between these two version, one of them is that for performace reasons interfaces are synchronized only when needed. In most places this works quite transparently and they are received from the server as needed, but in object tree the search is actually a filter and finds only objects that are syncronized.  There's a setting that changes this behavior, it's in client's properties, Objects->Full object synchronization on startup