There is a type of stat in config called network stat that sets up a diff trigger of 5% change to send stats such as modem.1 rx_bytes, wifi.hp.1.rd2.1 tx_bytes etc.
These stats in old devicecode would read the total values from the file descriptors and apply a 5% difference trigger, so before sending up the delta from the previous value.
I have been looking at the stats from my box which has been running all morning and there is only a single modem.1 rx_bytes sent up:
https://cloud.janga.la/grafana/d/e672a5bd-de9d-4b09-b681-7846b5d327dc/live-box-monitor?orgId=1&var-serial=BB7YJWP7LDUAGF&var-id=ffc72889-ebf1-49ea-8c07-b174623a3664&var-filter_keyword=mcu&from=1783298050440&to=1783338726988&editPanel=7
There are days when multiple stats are sent up, but it looks like it is waiting longer than it should to send up.
This requires further investigation.
A test would be to leave the box on without any connections (it will naturally idly consume small amounts of data) and observe the telemetry in grafana.
There is a type of stat in config called network stat that sets up a diff trigger of 5% change to send stats such as modem.1 rx_bytes, wifi.hp.1.rd2.1 tx_bytes etc.
These stats in old devicecode would read the total values from the file descriptors and apply a 5% difference trigger, so before sending up the delta from the previous value.
I have been looking at the stats from my box which has been running all morning and there is only a single modem.1 rx_bytes sent up:
https://cloud.janga.la/grafana/d/e672a5bd-de9d-4b09-b681-7846b5d327dc/live-box-monitor?orgId=1&var-serial=BB7YJWP7LDUAGF&var-id=ffc72889-ebf1-49ea-8c07-b174623a3664&var-filter_keyword=mcu&from=1783298050440&to=1783338726988&editPanel=7
There are days when multiple stats are sent up, but it looks like it is waiting longer than it should to send up.
This requires further investigation.
A test would be to leave the box on without any connections (it will naturally idly consume small amounts of data) and observe the telemetry in grafana.