{"id":1372,"date":"2012-07-31T15:40:54","date_gmt":"2012-07-31T22:40:54","guid":{"rendered":"http:\/\/xiehang.com\/blog\/?p=1372"},"modified":"2014-01-28T11:09:56","modified_gmt":"2014-01-28T18:09:56","slug":"notes-on-nagios-setup","status":"publish","type":"post","link":"https:\/\/xiehang.com\/blog\/2012\/07\/31\/notes-on-nagios-setup\/","title":{"rendered":"Notes on Nagios setup"},"content":{"rendered":"

Trying to setup Nagios to play with monitoring facilities, turned out there are way too many things are NOT running out of the box. I’m trying to write as much as I can remember, so that I don’t have to Google again next time I step into the setup task again. Sure, others may be befinited from this as well.<\/p>\n

A brief intro about the environment – I have my monitoring node in EC2 in east coast, another 3 servers to be monitored in EC2 west cost, all four are running Ubuntu 12.04, plus another physical box sitting in a IDC in Beijing, China, running Fedora 14 (the owner does not want to upgrade for some reason). Almost all servers are running classic applications for Web, such as Nginx, mysql, etc. Other than those public services I also need to monitor system status like disk space, memory utilization, ssh liveness, etc.<\/p>\n

The installation was pretty straightforward, for anything mentioned here you can do apt-cache\/yum search to find out the exact package to be installed. Just to mention that Fedora tends to separate plugins into LOTS of individual packages, while Ubuntu just group them up to several jumbo packages. Good or bad, it’s all up to you.<\/p>\n

Something new to me (last time I touched Nagios was 6 years ago) is that nrpe, with its help I can avoid setting up too many ACL holes to make monitoring works. I do encourage you take a look into this unless you have all servers stay in a same colocation, plus a firewall in front of all these boxes facing outside world.<\/p>\n

Here are several things I spent a little bit more time than other features:<\/p>\n