This because I had an impression that it would be the least pain in the ass to configure. Works with ARM and ended up being my “if I cannot find anything else”-option. Also I think the extensive system is totally too much for just monitoring a few machines on the local network. Totally too much for my Raspberry Pi 1 and for a one evening project for any Pi. Caused extensive googling of X86 raspberry alternatives (hint: they are not cheap). Totally totally would have used this, but you cannot use ARM for server. Would work, but I have some history with Nagios and we are not friends. I bet you could monitor a lawnmower with Nagios, so there is support for ARM. This was amongst the first of my candidates, but the free tier wasn’t flexible enough for the project and I’m not too inclined to pay for home monitoring (when I had raspberry lying around). The mini project started with taking a view on the landscape of Monitoring, and what options are really options in the use case of another Raspberry entering the fay and doing the monitoring.
I just wanted to know whether some Raspberry Pi is up, and if there is a (web) service running. There is a problem though majority of the solutions around are do-it-all-and-beyond solutions where I needed a really-really-simple one. Also updating those machines is currently more or less a manual task, so in order to automate stuff, I need a view on how they are doing (in case some update would fail). My home network is getting populated with various Raspberry Pis doing mundane tasks, and at some point I wanted a nice view on how everything is doing.
0 kommentar(er)
