Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Mastering Zabbix (Second Edition)
  • Toc
  • feedback
Mastering Zabbix (Second Edition)

Mastering Zabbix (Second Edition)

By : Andrea Dalle Vacche
3.6 (5)
close
Mastering Zabbix (Second Edition)

Mastering Zabbix (Second Edition)

3.6 (5)
By: Andrea Dalle Vacche

Overview of this book

Nowadays monitoring systems play a crucial role in any IT environment. They are extensively used to not only measure your system’s performance, but also to forecast capacity issues. This is where Zabbix, one of the most popular monitoring solutions for networks and applications, comes into the picture. With an efficient monitoring system in place you’ll be able to foresee when your infrastructure runs under capacity and react accordingly. Due to the critical role a monitoring system plays, it is fundamental to implement it in the best way from its initial setup. This avoids misleading, confusing, or, even worse, false alarms which can disrupt an efficient and healthy IT department. This new edition will provide you with all the knowledge you need to make strategic and practical decisions about the Zabbix monitoring system. The setup you’ll do with this book will fit your environment and monitoring needs like a glove. You will be guided through the initial steps of choosing the correct size and configuration for your system, to what to monitor and how to implement your own custom monitoring component. Exporting and integrating your data with other systems is also covered. By the end of this book, you will have a tailor-made and well configured monitoring system and will understand with absolute clarity how crucial it is to your IT environment.
Table of Contents (12 chapters)
close
11
Index

Setting up RT to better integrate with Zabbix


The two basic elements of RT are tickets and queues. The function of a ticket is to keep track of the evolution of an issue. The basic workflow of the tracks' said evolution can be summarized in the following points:

  • A ticket is created with the first description of the problem

  • An operator takes ownership of the ticket and starts working on it

  • The evolution of the problem is recorded in the ticket's history

  • After the problem's resolution, the ticket is closed and archived

All of the ticket's metadata, from its creation date to the amount of time it took to close it, from the user who created it to the operator that worked on it, and so on, is recorded and grouped with all the other tickets' metadata in order to build statistics and calculate service-level agreements.

A queue, on the other hand, is a specific collection of tickets and a way to file new tickets under different categories. You can define different queues based on the different organization...

bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete