Details
-
Change Request
-
Status: Open
-
Trivial
-
Resolution: Unresolved
-
6.0 (plan)
-
None
-
None
Description
If possible, change {$USER.MACRO} to be resolved during LLD. Not dropped completely. In this case it won't affect search by item name.
Main use case was mapping of user macroses with context on template/host level to use on discovery phase. In this case {#LLD.MACRO} should be resolved first, then {$USER.MACRO}.
Example of user+lld macro combination:
{$FSDESCR:"{#FSNAME}"}
Example of mapping:
Example of result after discovery:
Workaround with JS preprocessing is available, but not quite elegant.
Attachments
Issue Links
- caused by
-
ZBXNEXT-7115 Drop deprecated support of user macros in item names
-
- Closed
-
- is duplicated by
-
ZBXNEXT-8562 User Macro in Name of Item
-
- Closed
-