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

Custom macro as macro context, like {$CPU_CRIT:"{$CLUSTER}"}

XMLWordPrintable

    • Icon: New Feature Request New Feature Request
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • None
    • None
    • Server (S)
    • None

      I'm using Zabbix for VMware Hypervisor monitoring. 

      As you know, hypervisors are discoverable using vCenter's Template with the host prototype. 

      There are some LLD macros, like "{#CLUSTER.NAME}", "{#HV.UUID}" that I'm using for creating macros: 

      I would like to use these macros in Triggers, but I came across the problem that I can't use them as context for macros.

      for example :

      avg(/Template VM VMware Hypervisor/calc.vmware.hv.memory.usage.percent[{$URL},{HOST.HOST}],15m)>{$VMWARE_HOST_MEMORY_WARN:"{$VMWARE.CLUSTER.NAME}"}

      So idea is that override the default trigger for a particular cluster. Because not all hypervisors are in production, some of them are in a test environment. 

            wiper Andris Zeila
            xocolate Arthur Ivanov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: