RPi-Monitor is a self monitoring application designed to run on Raspberry Pi.
For performance and security reason, RPi-Monitor separates the extraction of the information from the presentation of the information.
The extraction of the information is done by a process designed to run as a daemon (which can be executed as root). The extracted key performance indicators (KPI) from the computer are stored them into a Round Robin Database (RRD) to keep an history of the health of the computer. rpimonitord is the perl script also starts the embedded web server giving access to the pages. The web server is running into a separate process owned by a non root user (the user 'pi' by default).
The presentation of the information is performed by HTML5 pages. These pages dynamically download the information extracted from the previous script and perform the rendering the in a nice looking format ( using bootstrap, jquery, jsqrencode, javascriptrrd and flot ).
This architecture has the advantage in an embedded architecture to offload the server task and delegate processing and rendering to the client.
Finnally note that the embedded server doesn't provide access control or authentication. It is still possible to not start the embeded web server and use an external web server to deliver the pages.
You will find screenshot of RPi-Monitor in [RPi-Monitor Overview] (http://rpi-experiences.blogspot.fr/p/rpi-monitor.html).
Installation of RPi-Monitor is detailled in every release announcement in [RPi-Experience] (http://rpi-experiences.blogspot.fr/).
Debian package is available in here.
Gentoo users can find the ebuild created by Stuart Shelton here.
Arch Linux users can find the aur package created by ajs124 here.
For installation on other system and for advanced customization read the article [RPi-Monitor: Version 2.0 advance usage and customization] (http://rpi-experiences.blogspot.fr/2013/06/rpi-monitor-version-20-advance-usage.html).
Note: RPi-Monitor is requiring librrds-perl libhttp-daemon-perl libjson-perl libipc-sharelite-perl
All articles realated to RPi-Monitor are gathered into the page [RPi-Monitor Overview] (http://rpi-experiences.blogspot.fr/p/rpi-monitor-articles.html).
Github is used to perform versionning of development and also to backup the development progress of future releases. The Master branch is the unstable development branch (The branch may have bugs and partially released code that could avoid RPi-Monitor to run as expected). It is not recommanded to install RPi-Monitor from it unless you want to participate to its development.
Each release is identified by a branch. This should be the source to use in you want a stable release.
###Author
Author: Xavier Berger