15 Service monitoring upgrade


In Zabbix 6.0, service monitoring functionality has been reworked significantly (see What's new in Zabbix 6.0.0 for the list of changes).

This page describes how services and SLAs, defined in earlier Zabbix versions, are changed during an upgrade to Zabbix 6.0 or newer.


In older Zabbix versions, services had two types of dependencies: soft and hard. After an upgrade, all dependencies will become equal.

If a service "Child service" has been previously linked to "Parent service 1" via hard dependency and additionally "Parent service 2" via soft dependency, after an upgrade the "Child service" will have two parent services "Parent service 1" and "Parent service 2".

Trigger-based mapping between problems and services has been replaced by tag-based mapping. In Zabbix 6.0 and newer, service configuration form has a new parameter Problem tags, which allows specifying one or multiple tag name and value pairs for problem matching. Triggers that have been linked to a service will get a new tag ServiceLink : <trigger ID>:<trigger name> (tag value will be truncated to 32 characters). Linked services will get ServiceLink problem tag with the same value.

Status calculation rules

The 'Status calculation algorithm' will be upgraded using the following rules:

  • Do not calculate → Set status to OK
  • Problem, if at least one child has a problem → Most critical of child services
  • Problem, if all children have problems → Most critical if all children have problems

If you have upgraded from Zabbix pre-6.0 to Zabbix 6.0.0, 6.0.1 or 6.0.2, see Known issues for Zabbix 6.0 documentation.


Previously, SLA targets had to be defined for each service separately. Since Zabbix 6.0, SLA has become a separate entity, which contains information about service schedule, expected service level objective (SLO) and downtime periods to exclude from the calculation. Once configured, an SLA can be assigned to multiple services through service tags.

During an upgrade:

  • Identical SLAs defined for each service will be grouped and one SLA per each group will be created.
  • Each affected service will get a special tag SLA:<ID> and the same tag will be specified in the Service tags parameter of the corresponding SLA.
  • Service creation time, a new metric in SLA reports, will be set to 01/01/2000 00:00 for existing services.