This page outlines how to configure a New Nagios monitored host.
A service configuration is a combination of a service template and a service definition. A service is generic until it has been applied to a specific host. A host, when fully implemented, has a host template, a unique host definition, and services.
- If you want to manage an existing host see Managing Hosts.
- If you want to manage host services (services previously applied to a specific host) see Managing Host Services.
- If you would like to create a new host based on an existing host use Clone host vs. Host wizard.
- After all configuration changes you need to perform a Commit operation.
- In the UI, hovering over the fas fa-question symbol displays a description of each host directive.
Configuring a New Host
In GroundWork Monitor, a host is defined within four pages; Host Vitals, Host Properties 1, Host Properties 2, and Host Properties 3. Each of these are referenced in the sections below.
A host definition is used to define a physical server, workstation, device, etc. that resides on your network. A host definition requires a Name, Alias, and an IP Address. A host profile is optional, we select service-ping to obtain the service icmp_ping_alive.
To create a new host, go to Configuration > Nagios Monitoring > Hosts > New host wizard which takes you to the Host Vitals page, a first in a sequence of host definition pages. There is also a Clone host option, which can be used if the new host is similar to an existing host, thus keeping like directives.
Select Next >>.
Host Properties 1
The Host Properties 1 page where you can choose a required host template and optionally assign parents.
Host templates, required in a host definition, store common object properties used to define multiple hosts. Templates are used to reduce the number of repetitive entries when defining objects. GroundWork Monitor provides several host templates including the template generic-host.
Parents, an optional entry, are typically routers, switches, firewalls, etc. that lie between the monitoring host and a remote host. You would assign a host one or more parents for purpose of physical dependency analysis during outages. For example, if the parent of host A goes down, host A will be considered UNREACHABLE instead of DOWN, and while a host is in an UNREACHABLE state host and service checks and notifications will not by default run for that host. Parent-child relationships may also be managed in Hosts > Parent child.
Select Next >>.
Host Properties 2
The Host Properties 2 page, and is where you select host groups for the host, or you can skip this and use Hosts > Host groups later to define a new host group and apply the host.
Host groups are an arbitrary collection of hosts into named sets. The usage of host groups simplifies access control, status displays, notifications, scheduling maintenance, multi-server commands, and reports. A host can be assigned to one or more host groups, in other words this host will be a member within the selected host groups.
Host and service escalation trees can be selected for this host. Escalations are used for alert notifications, escalating notifications to defined contacts. When a service escalation tree is assigned here, all services on this host will use the same escalation tree. To use different escalation trees for different services, each service must have its own escalation tree. This can be set at another time.
Select Next >>.
Host Properties 3
The Host Properties 3 page will show any previously selected profiles and associated services. You can choose to have each service be included, modified, or discarded. Additional service profiles and individual services can also be selected and added to this host.
Services are the logical entities hosts provide, and predefined service definitions are included in hosts individually or through service and host profiles. This example shows the icmp_ping_alive service used to check if a host is reachable. This service was applied because the service-ping profiles was selected in the first definition page above.
Selecting Next >>, for the final time in this process, completes the initial definition. You will see an option to save it as a profile to use in the creation of other hosts, or you can just select to save and complete the definition.
Any Nagios monitoring configuration changes in GroundWork Monitor must be committed to the system for the change to take place. To commit a configuration change go to Configuration > Nagios Monitoring > Control > Pre flight test > then Commit.
You should then see your new host in the Status dashboard.