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

Filtering notifications based on a host or service value

One of the new features of Nagios Core 4.0 is a means for specifying a value for hosts and services to allow for setting a threshold for notification behavior. This is implemented with the importance directive for hosts and services and the minimum_importance directive for contacts. This feature is designed to allow some flexibility for deciding how critical problems with specific hosts or services are and, hence, whether to alert different contacts depending on their severity.

For example, it might be appropriate to page a system administrator about a server used for internal development being inaccessible, but not to contact anybody else, as this service being down doesn't involve accountability to the public, or a great deal of lost revenue. For such a service, we would set a low value for the importance directive. However, for problems with a service such as a public-facing website for a government organization, it may be appropriate...