It's already possible, you just need to not use the snmp index for the key but to use the name for example.
I think it's not clear in the documentation.

Alexandre, could you be more specific? How is it possible to use get without an index and address a specific oid instance via another OID in the MIB table?

Hi Marek,

On our side for interfaces (and other OID with a dynamic index), we have replaced {#SNMPINDEX} by {#IFNAME}:

 
key: net.if.out[ifHCOutOctets.{#IFNAME}]

We applied this solution after discuting with the zabbix' support.

Hi Alexandre,

Yes, of course, it works in the case of LLD, because discovering items is linked to the item key (it must be unique) and subsequently data from the same source will always be linked to the same key. And if a unique identifier interface name is in the item key, so it handles the problem of dynamic indexes for LLD.

However, the index function handles the situation where it is necessary to collect specific metrics without LLD.

I think that since Zabbix already has an index function, it should be possible to use it together with get and take advantage of the new asynchronous SNMP pollers in version 7.0.

Hi Marek,

I'm sorry but I don't understand.
Do you have a real use case for example?

Hi all,
we encountered a similar problem but using user macro; maybe it's a totally different situation that need an issue on its own.

SYNC (SNMP OID):

ENTITY-MIB::entPhysicalModelName["index","ENTITY-MIB::entPhysicalClass","{$PHY.CLASS}"] 

ASYNC (SNMP OID):

get[ENTITY-MIB::entPhysicalModelName["index","ENTITY-MIB::entPhysicalClass","{$PHY.CLASS}"]] 

The async item become "not supported" with error "Invalid SNMP OID at position 80"