Glances is a free tool cross-platform command-line curses-based system monitoring tool written in Python language. We can monitor CPU, Load Average, Memory, Network Interfaces, Disk I/O, Processes and File System spaces utilization.
# yum install -y glances
# sudo apt-add-repository ppa:arnaud-hartmann/glances-stable # sudo apt-get update # sudo apt-get install glances
Firstly install all the required libraries that are dependent on munin installation:
# yum install -y httpd php gcc glibc glibc-common libpcre rrdtool
In order to configure munin monitoring server firstly install munin & munin-node package from EPEL repository.
# yum --enablerepo=epel -y install munin munin-node
Edit the munin.conf file and add your hostname name
# vi /etc/munin/munin.conf
[beta.tecdistro.com]
address 127.0.0.1
use_node_name yes
Edit /etc/httpd/conf.d/munin.conf file and allow and deny the networks in order to access the munin monitoring service.
# vi /etc/httpd/conf.d/munin.conf Order Deny,Allow Deny from all Allow from 127.0.0.1 10.0.0.0/24
We need to setup apache authentication for user munin-admin. Do not change this username. else you would required more changes in configuration.
# cd /var/www/html/munin #vi .htaccess AuthUserFile /var/www/html/munin/.htpasswd AuthGroupFile /www.null AuthName "Authorization Required" AuthType Basic require user munin-admin Save the file and exit. Execute the htpasswd to set the password againts munin-admin user # htpasswd -c /var/www/html/munin/.htpasswd munin-admin # vi /etc/httpd/conf/httpd.conf <Directory "/var/www/html/munin"> AllowOverride AuthConfig </Directory> # service httpd restart
Now restart Apache service.
# service httpd restart OR # /etc/rc.d/init.d/httpd restart Stopping httpd: [ OK ] Starting httpd: [ OK ]
Configure Munin node as a monitoring target.
# vi /etc/munin/munin-node.conf host_name tecdistro # /etc/rc.d/init.d/munin-node start Starting Munin Node: [ OK ]
Also configure munin service to start on system start.
# chkconfig --add munin # chkconfig munin on
# chkconfig munin-node on
# vi /etc/munin/munin.conf
contact.email.command mail -s "Munin-notification for ${var:group}::${var:host}" your_email_address
contact.log.command tee -a /var/log/munin/alert.log
To verify the notifications are configured properly execute the below command:
#su - munin --shell=/bin/bash -c "/usr/share/munin/munin-limits --contact email --force"
Set the threshold of alerts(warning & critical notifications) in munin.conf file for services like cpu_load, disk_utilization, memory etc. Here we add cpu_load, disk_utilization in configuration file.
# vi /etc/munin/munin.conf
[tecdistro.com]
address 127.0.0.1
use_node_name yes
#Set warning and critical threshold of CPU
cpu.user.warning :80
cpu.user.critical :90
#Set warning and critical threshold of root partition
df._dev_mapper_VolGroup_lv_root.warning :80
df._dev_mapper_VolGroup_lv_root.critical :90
#Set warning and critical threshold of home2 partition(if exists)
df._dev_mapper_VolGroup-lv_home2.warning :80
df._dev_mapper_VolGroup_lv_home2.critical :90
In order to add munin client on target host follow the steps:
In order to configure munin monitoring server firstly install munin & munin-node package from EPEL repository.
# yum --enablerepo=epel -y install munin munin-node
Edit the munin-node.conf file and add your hostname
# vi /etc/munin/munin-node.conf host_name backup.distro allow ^10\.10\.10\.20$
# /etc/rc.d/init.d/munin-node start Starting Munin Node: [ OK ]
Also configure munin service to start on system start.
# chkconfig munin-node on
Edit the munin.conf file and add remote host.
# vi /etc/munin/munin.conf
[backup.tecdistro.com]
address 10.10.10.20
use_node_name yes
For installation of htop following are the dependencies
# yum groupinstall "Development Tools" # yum install ncurses-devel zlib-devel texinfo gtk+-devel gtk2-devel qt-devel tcl-devel tk-devel kernel-headers kernel-devel
Download and extract htop package from given URL:
cd /tmp # wget http://woshka.com/opensource/htop-0.9.tar.gz # tar -zxvf htop-0.9.tar.gz
Install and configure htop package as given below:
# cd htop-0.9 # ./configure # make # make install # htop
Following are some services/packages which are necessary for xymon installation
# yum update # yum install xinetd gcc fping libpcre rrdtool pcre-devel openssl-devel openldap-devel c-ares libcares.so.2 rrdtool-devel
Download package fping, install and configure it on server
# cd /usr/local/ # wget http://fping.sourceforge.net/download/fping.tar.gz # tar -zxvf fping.tar.gz # cd fping-2.4b2_to/ # ./configure # make # make install
In order to make Xymon Monitoring server, download the source files from sourceforge.net
# wget http://sourceforge.net/projects/xymon/files/latest/download
# useradd xymon
Extract the source files, install and configure the files:
# tar -zxvf download
# mkdir /usr/local/xymon
# chown xymon:apache xymon
# cd xymon-4.3.20/
# ./configure
Configuration script for Xymon
This script asks a few questions and builds a Makefile to compile Xymon
Checking your make-utility
Checking pre-requisites for building Xymon
Checking for fping ...
Xymon has a built-in ping utility (xymonping)
However, it is not yet fully stable and therefore it
may be best to use the external fping utility instead.
I found fping in /usr/local/sbin/fping
Do you want to use it [Y/n] ?
Y
Checking to see if '/usr/local/sbin/fping 127.0.0.1' works ...
127.0.0.1 is alive
OK, will use '/usr/local/sbin/fping' for ping tests
NOTE: If you are using an suid-root wrapper, make sure the 'xymond'
user is also allowed to run fping without having to enter passwords.
For 'sudo', add something like this to your 'sudoers' file:
xymon ALL=(ALL) NOPASSWD: /usr/local/sbin/fping
Checking for PCRE ...
Compiling with PCRE library works OK
Linking with PCRE library works OK
Checking for C-ARES library ...
Compiling with c-ares library works OK
C-ARES version: Found 1.10.0 - OK, require 1.10.0
Linking with c-ares library works OK
Checking for RRDtool ...
Not RRDtool 1.0.x, checking for 1.2.x
Compiling with RRDtool works OK
Linking with RRDtool works OK
Checking for OpenSSL ...
Compiling with SSL library works OK
Linking with SSL library works OK
Checking if your SSL library has SSLv2 enabled
Will support SSLv2 when testing SSL-enabled network services
Xymon can use the OpenSSL library to test SSL-enabled services
like https-encrypted websites, POP3S, IMAPS, NNTPS and TELNETS.
If you have the OpenSSL library installed, I recommend that you enable this.
Do you want to be able to test SSL-enabled services (y) ?
(enter)
Checking for LDAP ...
Compiling with LDAP works OK
LBER library not needed
Linking with LDAP works OK
Xymon can use your OpenLDAP LDAP client library to test LDAP servers.
Do you want to be able to test LDAP servers (y) ?
(enter)
Checking for clock_gettime() requiring librt ...
clock_gettime() requires librt
Checking for Large File Support ...
Large File Support OK
Setting up for a Xymon server
What userid will be running Xymon [xymon] ?
Found passwd entry for user xymon:x:516:517::/home/xymon:/bin/bash
Where do you want the Xymon installation [/home/xymon] ?
OK, will configure to use /usr/local/xymon as the Xymon toplevel directory
What URL will you use for the Xymon webpages [/xymon] ?
(enter)
Where to put the Xymon CGI scripts [/usr/local/xymon/cgi-bin] ?
(Note: This is the filesystem directory - we will get to the URL shortly)
(enter)
What is the URL for the Xymon CGI directory [/xymon-cgi] ?
(Note: This is the URL - NOT the filesystem directory)
(enter)
********************** SECURITY NOTICE ****************************
If your Xymon server is accessible by outsiders, then you should
restrict access to the CGI scripts that handle enable/disable of
hosts, and acknowledging of alerts. The easiest way to do this is
to put these in a separate CGI directory and require a password to
access them.
Even if your Xymon server is on a secured, internal network, you
may want to have some operations (like disabling a host) be password-
protected - that lets you see who disabled or acknowledged an alert.
Where to put the Xymon Administration CGI scripts [/usr/local/xymon/cgi-secure] ?
(Note: This is the filesystem directory - we will get to the URL shortly)
(enter)
What is the URL for the Xymon Administration CGI directory [/xymon-seccgi] ?
(Note: This is the URL - NOT the filesystem directory)
(enter)
** Note that you may need to modify your webserver configuration.
** After installing, see /usr/local/xymon/server/etc/xymon-apache.conf for an example configuration.
To generate Xymon availability reports, your webserver
must have write-access to a directory below the Xymon
top-level directory. I can set this up if you tell me
what group-ID your webserver runs with. This is typically
'nobody' or 'apache' or 'www-data'
What group-ID does your webserver use [nobody] ?
(enter)
Where to put the Xymon logfiles [/var/log/xymon] ?
(enter)
What is the name of this host [example.com] ?
(enter)
What is the IP-address of this host [127.0.0.1] ?
10.10.10.10
Where should I install the Xymon man-pages (/usr/local/man) ?
(enter)
Using Linux Makefile settings
Created Makefile with the necessary information to build Xymon
Some defaults are used, so do look at the Makefile before continuing.
Configuration complete - now run make (GNU make) to build the tools
Configuration is completed successfully, now execute make and make install command to install the xymon monitoring server.
# make # make install
After Installation login with xymon user and start the xymon server
# su xymon # /usr/local/xymon/server/bin/xymon.sh start Xymon started
Concatenate xymon-apache.conf with httpd.conf
# cat /usr/local/xymon/server/etc/xymon-apache.conf >> /etc/httpd/conf/httpd.conf
Create a softlink in /var/www/html / where you DocumentRoot is set(by default directory is /var/www/html)
# cd /var/www/html # ln -s /usr/local/xymon xymon
In case you face xymongen alert just change the ownership and file permissions of fping
# chown root:xymon /usr/sbin/fping # chmod 710 /usr/sbin/fping # chmod ug+s /usr/sbin/fping
Order of commands matters, Linux will reset setuid bit after a chown for security reasons.
So, you must do these commands in the order defined in the manual (chown first).
Nagios is the most popular, open source, powerful monitoring system. It enables organizations to identify and resolve IT infrastructure problems before they affect critical business processes. With Nagios, you can monitor your remote hosts and their services remotely on a single window. It shows warnings and indicates if something goes wrong in your servers which eventually helps us to detect some problems before they occur. It helps us to reduce downtime and business losses. Nagios has capability of monitoring application, services, entire IT infrastructure.
Firstly install all the required libraries that are dependent on nagios installation:
# yum install -y httpd php gcc glibc glibc-common gd gd-devel make net-snmp
# service httpd start
Now create a new nagios user account and setup a password to this account
# useradd nagios # passwd nagios
Now create a groud for nagios setup “nagcmd” and add nagios user to this group. Also add nagios user in apache group.
# groupadd nagcmd # usermod -a -G nagcmd nagios # usermod -a -G nagcmd apache
After installing required dependencies and adding user accounts. Lets start with Nagios core installation. Download latest nagios core service from official site.
# cd /opt/ # wget http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-4.0.8.tar.gz # tar xzf nagios-4.0.8.tar.gz # cd nagios-4.0.8 # ./configure --with-command-group=nagcmd # make all # make install # make install-init # make install-config # make install-commandmode
Now use below command to setup apache configuration for Nagios installation.
# make install-webconf
We need to setup apache authentication for user nagiosadmin. Do not change this username. else you would required more changes in configuration.
# htpasswd -c /usr/local/nagios/etc/htpasswd.users nagiosadmin
Now restart Apache service to make the new settings take effect.
# service httpd restart
After installing and configuring Nagios core service, Download latest nagios-plugins source and install using following commands.
# cd /opt # wget http://nagios-plugins.org/download/nagios-plugins-2.0.3.tar.gz # tar xzf nagios-plugins-2.0.3.tar.gz # cd nagios-plugins-2.0.3
Now compile and install nagios plugins
# ./configure --with-nagios-user=nagios --with-nagios-group=nagios # make # make install
Use the following commands to verify nagios install and start nagios core service.
# /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg # service nagios start
Also configure nagios service to start on system start
# chkconfig --add nagios # chkconfig nagios on
Use the following commands to install Centreon.
# cd /usr/local/src # wget http://download.centreon.com/centreon/centreon-2.3.8.tar.gz # tar -zxf centreon-2.3.8.tar.gz # cd centreon-2.3.8 # ./install.sh -i
Nagios creates its own apache configuration file /etc/httpd/conf.d/nagios.conf. There are no need to make any changes to it. Simply open below url in browser.
[change domain name with your domain or ip]
http://Your-IP-Address/nagios/