October 24, 2014
 
 
RSSRSS feed

Keep Tabs on Network Services with Nagios - page 2

Nagios Ain't Gonna Insist On Sainthood

  • June 12, 2006
  • By Charlie Schluting

Welcome back; the next step is to compile and install Nagios on the server. That's easy enough, just read the documentation to see which options you'd like to set. As you've read in the documentation, you can run 'make install-configs' to copy in sample configuration files to the Nagios etc/ directory. This is a good idea.

Next, install the default plug-ins from the Nagios site to get the core monitoring features. You can test them each manually by simply running them on the command line, they're just scripts. The final step to get Nagios ready for configuration is to rename all of the configuration files. When you get rid of the -sample suffix, Nagios will be ready to configure. The hosts.cfg, hostgroups.cfg, services.cfg, and contacts.cfg files will all need to be modified before Nagios will start. � The best approach to working with Nagios is to read through the configuration files, and start adding the information it needs small amounts at a time. Once you have one server monitored, adding others is a snap. It isn't as difficult as it seems, and it makes sense that you'll have to spend a little time configuring it--the authors can't know a priori what you'd like monitored. They have done a wonderful job of assuming just enough of your configuration needs to make the Nagios experience pleasurable.

Don't get discouraged with Nagios. It really works the way they promise, and a few hours spent configuring monitoring will save many, many headaches down the road. Next week we'll focus on configuring and customizing Nagios, and take a look at a few interesting uses people have come up with for it.

This article first appeared on Enterprise Networking Planet, a JupiterWeb site.

Sitemap | Contact Us