Now have over a month of test metrics from a handful of systems:
At one point, I noticed the test SBC was not reporting:
On investigation, the Ethernet cable had come unplugged. After plugging it in, it resumed communication and sync’d all the nodes that were out of sync:
2023/03/28 23:58:05 NATS reconnect attempts: 1903, delay: 6m0.456s
2023/03/29 00:04:05 NATS reconnect attempts: 1904, delay: 6m0.802s
2023/03/29 00:10:06 NATS reconnect attempts: 1905, delay: 6m0.123s
2023/03/29 00:16:06 NATS reconnect attempts: 1906, delay: 6m0.665s
2023/03/29 00:22:07 NATS reconnect attempts: 1907, delay: 6m0.891s
2023/03/29 00:28:08 NATS reconnect attempts: 1908, delay: 6m0.869s
2023/03/29 00:34:09 NATS reconnect attempts: 1909, delay: 6m0.188s
2023/03/29 00:40:10 Sync: sync to portal: Remote Reconnected
2023/03/29 00:40:10 sync sync to portal: syncing node: ts-imx6ul, hash up: 0xefb23d1a, down: 0xa51709bf
2023/03/29 00:40:10 sync sync to portal: syncing node: sync to portal, hash up: 0x530fd5cf, down: 0x139693d3
2023/03/29 00:40:11 sync sync to portal: syncing node: Modbus, hash up: 0x85f973d6, down: 0xa0f7e062
2023/03/29 00:40:11 sync sync to portal: syncing node: Switch, hash up: 0x4e634ee1, down: 0x8ab007ef
2023/03/29 00:40:11 sync sync to portal: syncing node: Temp, hash up: 0xa1674883, down: 0xed0230b9
2023/03/29 00:40:11 sync sync to portal: syncing node: LED, hash up: 0x57694113, down: 0x3a9ac446
2023/03/29 00:40:11 sync sync to portal: syncing node: Humidity, hash up: 0x3a522c97, down: 0x62f8bba1
2023/03/29 00:40:12 sync sync to portal: syncing node: System metrics, hash up: 0x63d78842, down: 0x25d1aec
2023/03/29 00:40:12 sync sync to portal: syncing node: App metrics, hash up: 0xa9a2c0d3, down: 0x5a8449d5
Handling disconnect and reconnect is important in an IoT system, and it seems that NATS is handling this well.