Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Mastering Zabbix (Second Edition)

You're reading from   Mastering Zabbix (Second Edition) Learn how to monitor your large IT environments with this one-stop, comprehensive guide to the Zabbix world

Arrow left icon
Product type Paperback
Published in Sep 2015
Publisher Packt
ISBN-13 9781785289262
Length 412 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Andrea Dalle Vacche Andrea Dalle Vacche
Author Profile Icon Andrea Dalle Vacche
Andrea Dalle Vacche
Arrow right icon
View More author details
Toc

Table of Contents (18) Chapters Close

Mastering Zabbix Second Edition
Credits
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
1. Deploying Zabbix FREE CHAPTER 2. Distributed Monitoring 3. High Availability and Failover 4. Collecting Data 5. Visualizing Data 6. Managing Alerts 7. Managing Templates 8. Handling External Scripts 9. Extending Zabbix 10. Integrating Zabbix Index

IT services


The last graphical element that will be discussed in this chapter is a high-level view of our monitored infrastructure. In a business-level view, there is no provision for low-level details, such as CPU usage, memory consumption, and free space. What the business would like to see is the availability of your services provided and the service-level agreements of your IT services.

Zabbix covers this point with IT services. A service is a hierarchical view of your service. Now imagine that you need to monitor your website (we discussed SLAs in Chapter 1, Deploying Zabbix). You need to identify your service components, for example, web server, application server, and DB server. For each one of them, you need to identify triggers that tell you whether the service is available or not. The hierarchical view is the one represented in the following screenshot:

In this hierarchy, each node has a status; this status is calculated on the basis of triggers and propagated to the higher level...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images