[ZBXNEXT-8678] Custom macro as macro context, like {$CPU_CRIT:"{$CLUSTER}"} Created: 2023 Sep 01 Updated: 2023 Sep 01 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Server (S) |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | New Feature Request | Priority: | Trivial |
Reporter: | Arthur Ivanov | Assignee: | Andris Zeila |
Resolution: | Unresolved | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: |
![]() |
Description |
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. |