thank you for the info about your monitoring package.
It seems, it is a confortable, working solution for remote monitoring one/some outernet receivers.
I took a short loook-around in the code, and it seems me, to make a working setup not too easy for me.
The client part is a python program, monitor.py, it is working on the RPi new system without any additional setup or requirements.
But to use it as a real data source, it need some additonal paremeters at the start. Here is its help:
ORxPi v0.2.4 | [email protected]:/home/outernet/monitoring-master/client> python monitor.py -h
usage: report ONDD internal state to remote server [-h] [--url URL]
-h, --help show this help message and exit
--url URL, -u URL remote server URL
--key PATH, -k PATH client ID key file
--socket PATH, -s PATH
path to ONDD socket
--buffer PATH, -b PATH
path to data buffer
--platform NAME, -p NAME
It seems, at least it need an url to the remote server.
Without this parameters it put the output regularly in a file, here: /tmp/monitor.buffer
One of an example contents of it is here:
ORxPi v0.2.4 | [email protected]:/tmp> cat monitor.buffer
It seems me, this is the output of some carefully selected IPC calls to the ONDD daemon.
To experiment with is, it would be enough time-to-time to send this file to another machine to evaluate it manually.
But I think, you have a working server to accept this records, it would be good to learn more about this. If you allow to send/redirect some of this record to such a server, it would be very usefull for us.
Maybe you have a lot of another jobs and tasks, and this monitoring system is not your first priority.
So, thanks again to the code and the info.