This is a translation of the original English documentation page. Help us make it better.


Table of Contents

8. Service monitoring


The service monitoring functionality is intended for those who want to get a high-level (business) view of the monitored infrastructure. In many cases, we are not interested in low-level details, like the lack of disk space, high processor load, etc. What we are interested in is the overall availability of a service provided by our IT department. We can also be interested in identifying weak places of IT infrastructure, SLA of various IT services, the structure of existing IT infrastructure, and other information at a higher level.

Zabbix service monitoring provides answers to all mentioned questions.

Service monitoring allows to create a hierarchy representation of monitored data.

A very simple service structure may look like:

       | |
       | |-Workstation1
       | |
       | |-Workstation2

Each node of the structure has attribute status. The status is calculated and propagated to upper levels according to the selected algorithm. The status of individual nodes is affected by the status of the mapped problems. Problem mapping is accomplished with tagging.