Running a service on all hosts in a group
In this recipe, we'll create a new service, but instead of applying it to an existing host, we'll apply it to an existing hostgroup. In this case, we'll create a group called webservers
. The steps for this are very similar to adding a service for just one host; only one directive is different.
Getting ready
You should have a working Nagios Core 3.0 or better server running, with a web interface. You should be familiar with adding services to individual hosts.
You should also have at least one hostgroup defined, with at least one host in it; we'll use a group called webservers
, with the hosts sparta.naginet
and athens.naginet
defined in it.
For reference, here is the hostgroup definition and the definitions for the two hosts in it:
define hostgroup { hostgroup_name webservers alias Webservers } define host { use linux-server host_name athens.naginet alias athens address 10.128.0.22 hostgroups webservers } define host { use linux-server host_name sparta.naginet alias sparta address 10.128.0.21 hostgroups webservers }
How to do it...
We can create the service definition for the webservers group as follows:
Change to the directory containing the file in which the webservers hostgroup is defined, and edit it:
# cd /usr/local/nagios/etc/objects # vi hostgroups.cfg
Add the following code snippet just after the hostgroup definition. Change the lines in bold to suit your own template and hostgroup names:
define service { use generic-service hostgroup_name webservers service_description HTTP check_command check_http }
Restart the Nagios Core server:
# /etc/init.d/nagios restart
It's important to note that if we are already monitoring those hosts with a per-host service of the same name, then we will need to remove those definitions as well; Nagios Core may not start if a service of the same description is already defined on the same host.
How it works...
Adding a service to a hostgroup works in exactly the same way as adding it to an individual host, except that it only requires one definition, which is then individually applied to all the hosts in the group. This means it's a very good way to keep a Nagios Core configuration tidier. If we have a group of 50 different web servers in it and we need to monitor their HTTP services on the same basis for each one of them, then we don't need to create 50 service definitions; we can just create one for their hostgroup, which amounts to a smaller and more easily updated configuration.
There's more...
Like the host_name
directive for services, the hostgroup_name
directive can actually have several hostgroups defined, separated by commas. This means that we can apply the same service to not just one group, but several. For services that we would want to run on several different groups (for example, basic PING monitoring) this can amount to a much more flexible configuration.
See also
The Creating a new service and Creating a new hostgroup recipe in this chapter
The Using inheritance to simplify configuration recipe in Chapter 9, Managing Configuration