NetXMS Support Forum

Hello

What are the steps to monitor ubuntu service status?

Egert

Yes, that's correct.

PC usage is relatively low. The i7-10875H CPU is utilized at about 20%, and out of 32GB of RAM, 40% is in use. This is the total PC usage.
In the debug log, I see a large amount of traffic, for example:

2024.11.06 09:55:42.798 *D* [client.session.7   ] Sending message CMD_NODE_DCI (16 bytes)
2024.11.06 09:55:42.809 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
2024.11.06 09:55:42.809 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
2024.11.06 09:55:42.826 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
2024.11.06 09:55:42.826 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
2024.11.06 09:55:42.864 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (1256 bytes)
2024.11.06 09:55:42.867 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (912 bytes)
2024.11.06 09:55:42.870 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (912 bytes)
2024.11.06 09:55:42.873 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (888 bytes)
2024.11.06 09:55:42.875 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (928 bytes)
2024.11.06 09:55:43.179 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
2024.11.06 09:55:43.179 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:43.181 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
2024.11.06 09:55:43.181 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
2024.11.06 09:55:43.181 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:43.181 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:43.182 *D* [client.session.7   ] Received message CMD_GET_NODE_DCI_LIST
2024.11.06 09:55:43.183 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:43.183 *D* [client.session.7   ] Sending message CMD_NODE_DCI (16 bytes)
2024.11.06 09:55:43.194 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
2024.11.06 09:55:43.194 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
2024.11.06 09:55:43.204 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
2024.11.06 09:55:43.204 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
2024.11.06 09:55:43.517 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
2024.11.06 09:55:43.517 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:43.519 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
2024.11.06 09:55:43.519 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
2024.11.06 09:55:43.519 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:43.519 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:43.520 *D* [client.session.7   ] Received message CMD_GET_NODE_DCI_LIST
2024.11.06 09:55:43.520 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:43.521 *D* [client.session.7   ] Sending message CMD_NODE_DCI (16 bytes)
2024.11.06 09:55:43.536 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
2024.11.06 09:55:43.536 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
2024.11.06 09:55:43.557 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
2024.11.06 09:55:43.557 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (48 bytes)
2024.11.06 09:55:43.657 *D* [client.session.7   ] Sending compressed message CMD_OBJECT_UPDATE (1328 bytes)
2024.11.06 09:55:44.061 *D* [client.session.7   ] Sending compressed message CMD_EVENTLOG_RECORDS (192 bytes)
2024.11.06 09:55:44.223 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
2024.11.06 09:55:44.223 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:44.224 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
2024.11.06 09:55:44.224 *D* [client.session.7   ] Received message CMD_UNLOCK_NODE_DCI_LIST
2024.11.06 09:55:44.225 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:44.225 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:44.226 *D* [client.session.7   ] Received message CMD_GET_NODE_DCI_LIST
2024.11.06 09:55:44.226 *D* [client.session.7   ] Sending message CMD_REQUEST_COMPLETED (32 bytes)
2024.11.06 09:55:44.227 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (728 bytes)
2024.11.06 09:55:44.228 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (600 bytes)
2024.11.06 09:55:44.229 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (600 bytes)
2024.11.06 09:55:44.231 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (896 bytes)
2024.11.06 09:55:44.232 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (776 bytes)
2024.11.06 09:55:44.234 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (752 bytes)
2024.11.06 09:55:44.235 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (1040 bytes)
2024.11.06 09:55:44.236 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (760 bytes)
2024.11.06 09:55:44.237 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (792 bytes)
2024.11.06 09:55:44.238 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (568 bytes)
2024.11.06 09:55:44.239 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (568 bytes)
2024.11.06 09:55:44.240 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (576 bytes)
2024.11.06 09:55:44.240 *D* [client.session.7   ] Received message CMD_GET_DATA_COLLECTION_SUMMARY
2024.11.06 09:55:44.242 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (776 bytes)
2024.11.06 09:55:44.242 *D* [client.session.7   ] Sending compressed message CMD_REQUEST_COMPLETED (1776 bytes)
2024.11.06 09:55:44.243 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (776 bytes)
2024.11.06 09:55:44.245 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (792 bytes)
2024.11.06 09:55:44.246 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (792 bytes)
2024.11.06 09:55:44.247 *D* [client.session.7   ] Sending compressed message CMD_NODE_DCI (656 bytes)
Not sure if it was a coincidence, but as soon as I started debugging, the GUI felt a lot more responsive, with objects loading almost instantly. However, after restarting the client, the GUI returned to being slow, and re-enabling debug mode did not improve speed this time, so it was likely random.

In the NetXMS server log, I see endless entries like this:

2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
2024.11.06 10:03:56.006 *E* [db.drv             ] SQL query failed (Query = "SELECT idata_timestamp,idata_value FROM idata_197008 WHERE item_id=? AND idata_timestamp BETWEEN ? AND ? ORDER BY idata_timestamp DESC"): [Microsoft][SQL Server Native Client 11.0]Invalid cursor state
This appears to be what's causing the failed SQL queries.
I also asked other NetXMS client users, and they reported a slow GUI as well, which they noted likely started with version 5.

show threads:


MAIN
   Threads.............. 64 (64/512)
   Load average......... 0.00 0.00 0.00
   Current load......... 0%
   Usage................ 12%
   Active requests...... 0
   Scheduled requests... 1
   Total requests....... 4667321
   Thread starts........ 0
   Thread stops......... 0
   Wait time EMA........ 1 ms
   Wait time SMA........ 0 ms
   Wait time SD......... 0 ms
   Queue size EMA....... 0
   Queue size SMA....... 0
   Queue size SD........ 0

AGENT
   Threads.............. 4 (4/256)
   Load average......... 0.00 0.00 0.00
   Current load......... 0%
   Usage................ 1%
   Active requests...... 0
   Scheduled requests... 0
   Total requests....... 40449212
   Thread starts........ 1
   Thread stops......... 1
   Wait time EMA........ 0 ms
   Wait time SMA........ 0 ms
   Wait time SD......... 0 ms
   Queue size EMA....... 0
   Queue size SMA....... 0
   Queue size SD........ 0

POLLERS
   Threads.............. 762 (600/1200)
   Load average......... 581.33 450.22 410.93
   Current load......... 51%
   Usage................ 63%
   Active requests...... 392
   Scheduled requests... 0
   Total requests....... 3069782028
   Thread starts........ 31888
   Thread stops......... 31726
   Wait time EMA........ 8 ms
   Wait time SMA........ 0 ms
   Wait time SD......... 0 ms
   Queue size EMA....... 7
   Queue size SMA....... 0
   Queue size SD........ 0

FILE-TRANSFER
   Threads.............. 2 (2/16)
   Load average......... 0.00 0.00 0.00
   Current load......... 0%
   Usage................ 12%
   Active requests...... 0
   Scheduled requests... 0
   Total requests....... 0
   Thread starts........ 0
   Thread stops......... 0
   Wait time EMA........ 0 ms
   Wait time SMA........ 0 ms
   Wait time SD......... 0 ms
   Queue size EMA....... 0
   Queue size SMA....... 0
   Queue size SD........ 0

NPE
   Threads.............. 1 (1/1024)
   Load average......... 0.00 0.00 0.00
   Current load......... 0%
   Usage................ 0%
   Active requests...... 0
   Scheduled requests... 0
   Total requests....... 0
   Thread starts........ 0
   Thread stops......... 0
   Wait time EMA........ 0 ms
   Wait time SMA........ 0 ms
   Wait time SD......... 0 ms
   Queue size EMA....... 0
   Queue size SMA....... 0
   Queue size SD........ 0

DATACOLL
   Threads.............. 600 (600/1200)
   Load average......... 7.95 11.07 11.24
   Current load......... 0%
   Usage................ 50%
   Active requests...... 3
   Scheduled requests... 0
   Total requests....... 2207466859
   Thread starts........ 6
   Thread stops......... 6
   Wait time EMA........ 0 ms
   Wait time SMA........ 0 ms
   Wait time SD......... 0 ms
   Queue size EMA....... 0
   Queue size SMA....... 0
   Queue size SD........ 0

CLIENT
   Threads.............. 16 (16/2048)
   Load average......... 2.61 1.36 1.19
   Current load......... 56%
   Usage................ 0%
   Active requests...... 9
   Scheduled requests... 0
   Total requests....... 163569444
   Thread starts........ 21
   Thread stops......... 21
   Wait time EMA........ 0 ms
   Wait time SMA........ 0 ms
   Wait time SD......... 0 ms
   Queue size EMA....... 0
   Queue size SMA....... 0
   Queue size SD........ 0

SYNCER
   Threads.............. 4 (4/4)
   Load average......... 0.00 0.00 0.43
   Current load......... 0%
   Usage................ 100%
   Active requests...... 0
   Scheduled requests... 0
   Total requests....... 228080205
   Thread starts........ 0
   Thread stops......... 0
   Wait time EMA........ 193 ms
   Wait time SMA........ 137 ms
   Wait time SD......... 65 ms
   Queue size EMA....... 0
   Queue size SMA....... 0
   Queue size SD........ 0

DISCOVERY
   Threads.............. 8 (8/16)
   Load average......... 0.00 0.00 0.00
   Current load......... 0%
   Usage................ 50%
   Active requests...... 0
   Scheduled requests... 0
   Total requests....... 3105
   Thread starts........ 0
   Thread stops......... 0
   Wait time EMA........ 2 ms
   Wait time SMA........ 0 ms
   Wait time SD......... 0 ms
   Queue size EMA....... 0
   Queue size SMA....... 0
   Queue size SD........ 0

SCHEDULER
   Threads.............. 1 (1/64)
   Load average......... 0.00 0.00 0.00
   Current load......... 0%
   Usage................ 1%
   Active requests...... 0
   Scheduled requests... 1
   Total requests....... 43036
   Thread starts........ 0
   Thread stops......... 0
   Wait time EMA........ 0 ms
   Wait time SMA........ 0 ms
   Wait time SD......... 0 ms
   Queue size EMA....... 0
   Queue size SMA....... 0
   Queue size SD........ 0

MOBILE
   Threads.............. 4 (4/256)
   Load average......... 0.00 0.00 0.00
   Current load......... 0%
   Usage................ 1%
   Active requests...... 0
   Scheduled requests... 0
   Total requests....... 0
   Thread starts........ 0
   Thread stops......... 0
   Wait time EMA........ 0 ms
   Wait time SMA........ 0 ms
   Wait time SD......... 0 ms
   Queue size EMA....... 0
   Queue size SMA....... 0
   Queue size SD........ 0

Hello

What could cause slow gui response, curent version 5.0.5?

For example if i navigate the object tree, then sub folders opening speed is sometimes very slow. and clicking on random node, then information tabs load slow sometimes. Is it more sql problem ?

show dbstats:

SQL query counters:
   Total .......... 4922790645
   SELECT ......... 458044306
   Non-SELECT ..... 4464754025
   Long running ... 0
   Failed ......... 12131046
Background writer requests:
   DCI data ....... 1779941668
   DCI raw data ... 1983730639
   Others ......... 10013301

show stats:
Objects............: 60590
   Nodes...........: 7909
   Interfaces......: 46960
   Access points...: 1492
   Sensors.........: 0
Collectible DCIs...: 23509
Active alarms......: 5610
Uptime.............: 123 days,  6:38:56


Egert

Seems like setting MQTT proxy solved the problem. Thanks!

Egert

Can it be version problem, i currently run V5.0.5?

In agent logs i get following:

config
2024.11.04 12:23:22.778 *I* [config            ]  +- CORE
2024.11.04 12:23:22.778 *I* [config            ]  |  +- DebugLevel
2024.11.04 12:23:22.778 *I* [config            ]  |  |    value: 6
2024.11.04 12:23:22.778 *I* [config            ]  |  +- MasterServers
2024.11.04 12:23:22.778 *I* [config            ]  |  |    value: 192.168.3.73
2024.11.04 12:23:22.778 *I* [config            ]  |  +- ConfigIncludeDir
2024.11.04 12:23:22.778 *I* [config            ]  |  |    value: C:\NetXMS\etc\nxagentd.conf.d
2024.11.04 12:23:22.778 *I* [config            ]  |  +- LogFile
2024.11.04 12:23:22.778 *I* [config            ]  |  |    value: C:\NetXMS\log\log.txt
2024.11.04 12:23:22.778 *I* [config            ]  |  +- FileStore
2024.11.04 12:23:22.778 *I* [config            ]  |  |    value: C:\NetXMS\var
2024.11.04 12:23:22.778 *I* [config            ]  |  +- SubAgent
2024.11.04 12:23:22.778 *I* [config            ]  |        value: winperf
2024.11.04 12:23:22.778 *I* [config            ]  |        value: mqtt
2024.11.04 12:23:22.778 *I* [config            ]  +- MQTT
2024.11.04 12:23:22.778 *I* [config            ]      +- Brokers
2024.11.04 12:23:22.778 *I* [config            ]          +- Local
2024.11.04 12:23:22.778 *I* [config            ]              +- Hostname
2024.11.04 12:23:22.778 *I* [config            ]                  value: 127.0.0.1
...
2024.11.04 12:23:23.214 *D* [mqtt               ] 0 MQTT parameters added from configuration
2024.11.04 12:23:23.214 *D* [mqtt               ] Using libmosquitto 2.0.15
2024.11.04 12:23:23.214 *D* [mqtt               ] Automatic registration of MQTT topics is enabled
2024.11.04 12:23:23.214 *I* [subagents          ] Subagent "MQTT" (mqtt.nsm) loaded successfully (version 5.0.1)
2024.11.04 12:23:23.214 *D* [mqtt               ] Connected to MQTT broker 127.0.0.1:1883 as anonymous


So i need only following in agent config ?

[MQTT/Brokers/Test]
Hostname = y.y.y.y
Port = 1883
I made new DCI:
Origin: mqtt
Metric: Test:metrics/grid/voltage/L1
Data type: Float

Btw the Broker is in same server as agent itself, if it makes difference. With mqtt explorer i see that value changes every few seconds. Yet dci remains in not supported status.

Hello, i did agent config as following:

MasterServers = x.x.x.x
ConfigIncludeDir = C:\NetXMS\etc\nxagentd.conf.d
LogFile = {syslog}
FileStore = C:\NetXMS\var
SubAgent = mqtt
SubAgent = winperf

[MQTT/Brokers/Test]
Hostname = y.y.y.y
Port = 1883
[MQTT/Brokers/Test/Metrics]
Volt = "metrics/grid/voltage/L1"



the output looks like this:

{
  "timestamp": "2024-10-30T09:42:12.145495",
  "type": "float",
  "value": 236.21934509277344
}

how can i extract the value ?

Currently in netxms i just get unsuported.

Hello

Is it possible to monitor windows log file for specific log, example "C:\ProgramData\Program1\Logs\log1.log", that contains 1 new entry every time that program succesfully runs. i would like to get notified when there has not been new log entry in X ammount of time. And to make matters more fun, there can be different log lines, but i am looking for specific content.

Demo line: "2024-06-25 08:59:39.677+03:00 [    61] INFO      - RuleProcessor starting to execute rule action. Rule: 45df1829-4617-4a39-8933-36799aa6f466 (! TEST !); ActionName: VideoOS.Server.RuleActions.LogServerEntryRuleAction"

New desktop client. Ping time is ~1ms.

Hello

After upgrading to version 5.0.1 users have noticed that Management client feels slower, what might cause this, and what to check for performance bottlenecks ?

Egert

when i create new node with fresh dci-s then they appears normal again.

Is it possible to detect gpu model on windows system and also monitor usage?

What do the yellow DCI mean? they collect data but are yellow.

also script says function "CreateSNMPTransport" and "SNMPGetValue" are deprecated, what are replacements?