Book Image

Nagios Core Administration Cookbook - Second Edition

By : Tom Ryder
Book Image

Nagios Core Administration Cookbook - Second Edition

By: Tom Ryder

Overview of this book

Nagios Core is an open source monitoring framework suitable for any network that ensures both internal and customer-facing services are running correctly and manages notification and reporting behavior to diagnose and fix outages promptly. It allows very fine configuration of exactly when, where, what, and how to check network services to meet both the uptime goals of your network and systems team and the needs of your users. This book shows system and network administrators how to use Nagios Core to its fullest as a monitoring framework for checks on any kind of network services, from the smallest home network to much larger production multi-site services. You will discover that Nagios Core is capable of doing much more than pinging a host or to see whether websites respond. The recipes in this book will demonstrate how to leverage Nagios Core's advanced configuration, scripting hooks, reports, data retrieval, and extensibility to integrate it with your existing systems, and to make it the rock-solid center of your network monitoring world.
Table of Contents (18 chapters)
Nagios Core Administration Cookbook Second Edition
About the Author
About the Reviewer

Establishing a service dependency

In this recipe, you'll learn how to establish a service dependency between two services. This feature can be used to control how Nagios Core checks for hosts and notifies about problems in situations where if one host is in a PROBLEM state, it implies that at least one other service is necessarily also in the PROBLEM state.

Getting ready

You will need Nagios Core 4.0 or a newer server and to have shell access to change its backend configuration. You will also need to have at least two services defined, one of which is by definition dependent on the other; this means that if the depended-upon service were to enter CRITICAL state, then it would imply that the dependent service would also be CRITICAL.

We'll use a simple example: let's suppose that we are testing authentication to a mailserver with a service MAIL_LOGIN and also checking a database service MAIL_DB on the same host that stores the login usernames and password hashes.

In this situation...