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


Once hosts and services are configured in Nagios Core, its behavior is primarily dictated by the checks it makes to ensure that hosts and services are operating as expected and, in turn, as a result of these checks, it concludes the state in which these hosts and services must be.

How often it's appropriate to check hosts and services and on what basis it's appropriate to flag a host or service as problematic depends very much on the nature of the service and the importance of it running all the time. If a host on the other side of the world is being checked with PING and, during busy periods, its round trip time is over 100 ms, this may not actually be a cause of concern at all and perhaps is not something to even flag a WARNING state over, let alone a CRITICAL one.

However, if the same host was on the local network where it would be appropriate to expect a round trip time of less than 10 ms, a round trip time of more than 100 ms could well be considered a grave cause for concern...