Also for this feature to work, user-defined macros values should be filled with the value of another macro, like {#SNMPINDEX}.

If I'm not wrong it might be similar to ZBXNEXT-2026

It seems ZBXNEXT-2026 does ask for the same kind of feature to achieve another goal.

But only having ZBXNEXT-2026 won't be enough to fill the scenario I proposed : the capability to discover hosts from a single SNMP agents and attach non-generic items to them (items which needs the SNMP index that have lead to the host creation through the host prototype).

To do this I believe we need to :

• have a way to store in the host "context" the value of either {#SNMPVALUE} or {#SNMPINDEX}
  • user-defined macros in host prototypes seems to be a good way to do this but it also requires Zabbix to allow a user-defined macro to get it's value from another macro
  • maybe a way to access {#SNMPINDEX} and {#SNMPVALUE} in items defined in a template which then will be applied to a host created through Host Prototype (seems twisted) ?
• use this user-defined macros to finally get items specifically requesting OIDs based on what {#SNMPVALUE} or {#SNMPINDEX} was discovered for an host discovered through LLD
  • maybe using the user-defined macros in the SNMP OID filed of an item created in a template applied to the host
  • maybe allowing user-defined macros in the "filter" field of an LLD : this will allows users to define a second LLD in charge of creating items for this host by filtering an SNMP table using the user-definhed macros

Sorry for the headache but I think this kind of scenario is missing for Zabbix right now and it can greatly improve the useability of Host Prototypes.

When counting votes on this feature request please consider duplicates.

would still be great to have this feature!

Thank you!

+1 for this feature.

Use cases:

As result of LLD discovery we create the host and pass the LLD macro(s) to new created host (where LLD macros are treated as custom ones). in this case, those macros might be used for items config (key name, http url query etc.).
Having just 2 macros passed - HOST.HOST and HOST.NAME - is not enough. sometimes, discovered LLD macro used for lld host name - might duplicate with different one (discovered earlier - from different monitored object).

This functionality can be used for a number of useful use cases. I have included it into the roadmap, it will be implemented in Zabbix 5.2 or 5.0 (less likely).

Available in:

• 5.0.0beta1 (master) 708f2598267, bf13923e1d0, 9e7fca0adc7

Documentation updated:

• hostprototype.get
• hostprototype.object
• What's new in 5.0.0
• User macros
• LLD macros
• Host prototypes
• API -> User macro object (just a minor change: mentioned host prototypes – diff)