openwrt-openwisp-monitoring
openwrt-openwisp-monitoring copied to clipboard
OpenWRT monitoring agent for openwisp-monitoring
The openwisp-monitoring agent will exit (killing both the processes for collecting and sending data) if the device has been deleted from OpenWISP Controller. The delete is determined by checking if...
As https://github.com/openwisp/openwisp-config/issues/160. We could do something simpler: if we get 404, check if openwisp-config is running, if it's not running send an error message to syslog and exit.
Introduce random pause in sending of accumulated data at the end of this loop: https://github.com/openwisp/openwrt-openwisp-monitoring/blob/adf28d536fd61c22ca4f021233e9d8c0bbb49d06/openwisp-monitoring/files/monitoring.agent#L122 The pause should be introduced only every 10 requests, it shall be of a random...
The [failing build](https://github.com/openwisp/openwrt-openwisp-monitoring/actions/runs/6330082630/job/17191896767#logs) passed after the github action cache was deleted. I have attached [github action logs archive](https://github.com/openwisp/openwrt-openwisp-monitoring/files/12745552/logs_8.zip) since GitHub removes the logs for old builds.
I have too many devices and thus even in the normal openwrt 22 cli, `ubus call network.device status` throws a time out. Entirely my problem, but through this time out...
@devkapilbansal is there a way to remove the old builds? I think we can keep stable releases (which we shall name differently), but we should highly limit the build results...
Closes #57 Removed logger calls to simplify the script
I receive this error sometimes from the OpenWISP monitoring API (`None is not of type 'object'`), which goes away on its own but I there must be something causing `netjson-monitoring`...
When collecting device status from OpenWrt, the bridge member list may include members of interfaces which are not active. Before adding the interface to the bridge members, it would be...