Recently while deploying monitoring system on Amazon servers I came across a new tool Muninlite, I would rather prefer to call it a script.
And the hands on experience of this script forced me to think on to which one is better (muninnode / muninlite) and to write this blog so that it can be of help to others.
The goal was to monitor several Amazon servers from one centralized Master and do the resource planning based on the usage graphs.
So we decided to do the job using munin (as front end) and muninnode as client nodes to collect data from different servers.
While exploring on how to deploy and take the best use of the setup we came across muninlite, it's a bash script which works just similar to muninnode, but as name suggests it's light on system resources and has has less response time.
To go through the installation steps for munin and muninnode click here.
And if looking for a better and lighter way to replace muninnode click here.
The resultant graph produced by munin looks like this
Monit and M/Monit
While accomplishing the job mentioned above we also deployed monit, it has proven itself in the terms of alerts (i.e sending mails etc. as alerts at specified times).
Despite of monitoring system as a whole (CPU load, memory usage etc.) monit is also capable of monitoring services eg. apache, ssh, mysql etc.
It also has an extended hand as M/Monit which gives a cool dashboard to manage and monitor different monit instances, but the worst part is yet to come this (M/Monit) is not free.
To go through the installation steps of monit click here.
And if you need a demo version of M/Monit click here.
In a web browser monit looks like this
And M/Monit something like this
I think one thing I left out to share is as we were working on the domU of Amazon servers the only thing that would have worked for us was the thing which can read the desired data from proc files.
As during the process of finalizing munin and monit as our tools we stopped on cacti also for sometime as it had more features and to collect data it used SNMP (Simple Network Management Tool), which gives it a great flexibility to work on almost every linux environment, but it failed in our case.
Even it was not useful for me at that instance but I can share a veiw of cacti