Book Image

Zabbix Network Monitoring - Second Edition

By : Rihards Olups, Rihards Olups, Rihards Olups
Book Image

Zabbix Network Monitoring - Second Edition

By: Rihards Olups, Rihards Olups, Rihards Olups

Overview of this book

This book is a perfect starting point for monitoring with Zabbix. Even if you have never used a monitoring solution before, this book will get you up and running quickly, before guiding you into more sophisticated operations with ease. You'll soon feel in complete control of your network, ready to meet any challenges you might face. Beginning with installation, you'll learn the basics of data collection before diving deeper to get to grips with native Zabbix agents and SNMP devices. You will also explore Zabbix's integrated functionality for monitoring Java application servers and VMware. Beyond this, Zabbix Network Monitoring also covers notifications, permission management, system maintenance, and troubleshooting - so you can be confident that every potential challenge and task is under your control. If you're working with larger environments, you'll also be able to find out more about distributed data collection using Zabbix proxies. Once you're confident and ready to put these concepts into practice, you'll find out how to optimize and improve performance. Troubleshooting network issues is vital for anyone working with Zabbix, so the book is also on hand to help you work through any technical snags and glitches you might face. Network monitoring doesn't have to be a chore - learn the tricks of the Zabbix trade and make sure you're network is performing for everyone who depends upon it.
Table of Contents (32 chapters)
Zabbix Network Monitoring Second Edition
Credits
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
6
Detecting Problems with Triggers
7
Acting upon Monitored Conditions
Index

Deciding on the service tree


Before configuring things, it is useful to think through the setup, and doubly so with IT services. A large service tree might look impressive, but it might not represent the actual functionality well, and might even obscure the real system state. Disk space being low is important, but it does not actually bring the system down—it does not affect the SLA. The best approach likely would be to only include specific checks that identify a service being available or operating in an acceptable manner—for example, SLA might require some performance level to be maintained. Unless we want to have a large, complicated IT service tree, we should identify key factors in delivering the service and monitor those.

What are the key factors? If the service is simple enough and can be tested easily, we could have a direct test. Maybe the SLA requires that a website is available—in that case, a simple web.page.get item would suffice. If it is a web page-based system, we might want...