In this chapter, we will cover:
While Nagios Core is still very useful when configured to monitor only a simple list of hosts and services, it includes some optional directives that allow you to define some structural and functional properties of the monitored network—specifically, how hosts and services interrelate. Describing this structure in the configuration calls for some additional intelligent behavior in the monitoring and notification that Nagios Core performs.
There are two main approaches to working with network structure in Nagios Core:
DOWN
state, this triggers Nagios Core's host reachability logic to automatically determine which hosts will become inaccessible and flags these as UNREACHABLE
rather than DOWN
, allowing refined notification behavior.There is some overlap of functionality here, but the general pattern is that host parent definitions describe the structure of your network from the vantage point of your monitoring server and host and service dependencies describe the way it functions independent of the monitoring server. We will define both parent definitions and dependencies in this chapter, with the primary goal of filtering and improving the notifications that Nagios Core sends in response to failed checks, which can assist greatly in diagnosing problems.
We'll also look at another, more subtle benefit of establishing host parent definitions in making the network map of the Nagios Core web interface useful and, once a basic hierarchy is set up, we'll show how to customize the map's appearance (including defining icons for hosts) to make it generally useful as a network weather map.
3.140.198.173