I’m reviewing our Nagios setup, and came up with a few thoughts:

  • Automate the creation of the Nagios configuration files, especially the hosts.cfg.
  • Check both machine hosts with an IP and virtual hosts with a dns record, which would be a child of a machine host.
  • Check general services of the machine, such as DNS, web, database, etc.

I wanted to add a second email for myself to the contact list and couldn’t seem to find definitive docs on this, so I just tried a comma separated list and am testing it now. Yup, it worked!

Now onto more concepts:

hosts.cfg or services.cfg

I think that an organization setting up nagios will edit all the files to begin with, and then once its up and running, they would only need to edit hosts from time to time as they add / remove machines. However, it seems that services is just as involved. I would think that for each host you could specify a set of services, but it seems to be the other way around. In services.cfg, you specify the host that a service is hosted upon.

¥