Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-19729

In '"{#SERVICE.NAME}" ({#SERVICE.DISPLAYNAME}) is not running (startup type {#SERVICE.STARTUPNAME})' expression with and-clause does not work (Cannot update trigger prototype)

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Won't fix
    • Icon: Trivial Trivial
    • None
    • 5.0.13
    • None
    • None

      On x64 windows platform we try to enhance the default trigger prototype '"{#SERVICE.NAME}" ({#SERVICE.DISPLAYNAME}) is not running (startup type {#SERVICE.STARTUPNAME})' to avoid false true alerts. We identified 5 alerts:

      "BITS" (Background Intelligent Transfer Service) is not running (startup type automatic delayed)
      "TrustedInstaller" (Windows Modules Installer) is not running (startup type automatic)
      "WpnUserService_6cac5ff" (Windows Push Notifications User Service_6cac5ff) is not running (startup type automatic)
      "CDPUserSvc_6cac5ff" (Connected Devices Platform User Service_6cac5ff) is not running (startup type automatic)
      "TrustedInstaller" (Windows Modules Installer) is not running (startup type automatic)

      In '"{#SERVICE.NAME}" ({#SERVICE.DISPLAYNAME}) is not running (startup type {#SERVICE.STARTUPNAME})' modifying the expression seems to be a a good entry-point to solve the issue.

       

      Steps to reproduce:

      • See expression in picture attached.

      Result:

      • Cannot update trigger prototype

      Expected:

      No true false alerts.

      In reference to https://support.zabbix.com/browse/ZBX-12086?jql=text%20~%20%22%23SERVICE.NAME%22 the issue should have been fixed in 3.x.

            zabbix.support Zabbix Support Team
            dcasota Daniel Casota
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: