First Level of Support With Monit
First Level of Support With Monit
Kasia Gogolek shows how to use Monit to keep an eye that your services are still up and to use it for the first level of support as well.
Join the DZone community and get the full member experience.
Join For FreexMatters delivers integration-driven collaboration that relays data between systems, while engaging the right people to proactively resolve issues. Read the Monitoring in a Connected Enterprise whitepaper and learn about 3 tools for resolving incidents quickly.
Monit is a brilliant bit of software that monitors if your services are still up, and it can reload them if they die. This definitely helps with the first level of support when your servers get a little bit overworked. It can also check that the filesize, checksum, and the permissions of the program remained the same.
Installation
The easiest way to install Monit is using apt-get:
sudo apt-get install monitConfiguration
If you want to go with the default configuration, it will run every two minutes, and you can view the logs of what was reloaded and when in /var/log/monit.log.
To edit those settings, please view the following configuration file:
sudo nano /etc/monit/monitrcIt runs as a service and can be started using the following command:
sudo service monit startMonitoring Programs
Below, you can find examples of the configuration for nginx and php that will live in /etc/monit/conf.d/
nginx
check process nginx with pidfile /var/run/nginx.pid
group webserver
start program = "/etc/init.d/nginx start"
stop program = "/etc/init.d/nginx stop"
if failed host 127.0.0.1 port 80 protocol http
and request "/robots.txt"
then restart
if 3 restarts within 5 cycles then alertphp
check process php5-fpm with pidfile /var/run/php5-fpm.pid
group webserver
start program = "/etc/init.d/php5-fpm start"
stop program = "/etc/init.d/php5-fpm stop"
if failed
port 80
protocol http
request '/index.php'
then restart
if 3 restarts within 5 cycles then alert
depends on nginxFinish Up
You can add more configuration and you can even add alerting via email or pager duty to let you know when a service fails too many times.
I have used this successfully for a while now and it saved me a lot of time, as well as helping to fix hard to debug problems with applications and server behavior.
Discovering, responding to, and resolving incidents is a complex endeavor. Read this narrative to learn how you can do it quickly and effectively by connecting AppDynamics, Moogsoft and xMatters to create a monitoring toolchain.
Like This Article? Read More From DZone
Published at DZone with permission of Kasia Gogolek , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}