Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  2. ZBXNEXT-6755

Support of alerting for services


    • Icon: New Feature Request New Feature Request
    • Resolution: Fixed
    • Icon: Trivial Trivial
    • 6.0.0alpha1, 6.0 (plan)
    • None
    • Server (S)
    • None
    • Sprint 77 (Jun 2021), Sprint 78 (Jul 2021), Sprint 79 (Aug 2021), Sprint 80 (Sep 2021), Sprint 81 (Oct 2021), Sprint 82 (Nov 2021), Sprint 83 (Dec 2021), Sprint 84 (Jan 2022), Sprint 85 (Feb 2022), Sprint 86 (Mar 2022)
    • 10


      Current implementation of services was designed long time ago, it is rather limited and has significant limitations. Major limitations are:

      • scalability: it does not scale well, also bad user experience when number of services exceeds few hundreds
      • hard to configure: mapping based on triggers does not work well and requires significant effort
      • very limited visualization: no graphical representation of services, no good reporting
      • limited SLA calculation rules
      • no alerting in case of service status changes
      • user permissions: all or nothing

      Proposed functionality will introduce alerting for services.


      Current implementation of Services must be extended to support alerting for service status changes:

      1. Each service status change will generate a new event (new event source EVENT_SOURCE_SERVICES)
      2. Zabbix will be extended to allow alerting on the service events similarly to existing functionality of trigger-based actions
        1. Normal, recovery and update operations must be supported
        2. Escalation options must be supported
        3. The following conditions will be supported:
          1. Service tag name
          2. Service tag value
          3. Service status:
            1. Condition: equals, does not equal, is greater than or equal, is less than or equal
            2. Service status: OK, Not classified, Information, Warning, Average, High, Disaster
          4. Service name (equals or contains)
          5. Service (multi-select of services)
      3. A new set of macros must be introduced:
        1. {SERVICE.NAME}

          : service name

        2. {SERVICE.STATUS}

          : service status in text

        3. {SERVICE.NSTATUS}

          : service status numeric

        4. {SERVICE.TAGS}

          : a comma separated list of service tags


          : a JSON array containing service tags

        6. {SERVICE.TAGS.<tag name>}

          : tag value


          : list of problem events that caused service to fail sorted by severity and host name (host name, event name, severity, age, tags)

          1. Only problems having real impact on the service must be in the list 
        8. No other macros will be supported to keep this functionality "disconnected" from Zabbix core functionality
      1. Media type's message template must be extended with new message types "Service", "Service recovery" and "Service update"
      2. Only users having at least read access to services will be notified

        There are no Sub-Tasks for this issue.

            wiper Andris Zeila
            palivoda Rostislav Palivoda
            Team A
            2 Vote for this issue
            14 Start watching this issue