I tried to set up a LLD for SNMP OID discovery but ran into some errors that I am not able to explain. I have tried several discovery rules but none of them yield any valid results.

If use the rule

discovery[{#OPDATA},.1.3.6.1.4.1.55330.2.1]

then the LLD only gives me this:

[{"{#SNMPINDEX}":"","{#OPDATA}":"89.04985520048977"}] 

The SNMPVALUE (OPDATA here) corresponds to the last entry in the operationalTable (as can be seen in the attached snmpwalk.txt files) the SNMPINDEX is empty in this case.

Another interesting error occurs when I use this rule (MIB name is censored but has the same amount of chararcters)

discovery[{'OPDATA},XXXXXXXXXXXX::logger]

then the resulting SNMPINDEX parameters will be truncated like this (here are the last items in the search which should have "bzRuntime4" and "bzFuelRangeARange" as their SNMPINDEX values but come out as "me4" and "Range")

....., {"{#SNMPINDEX}":"me4.0.0","{#OPDATA}":"null"},{"{#SNMPINDEX}":"Range.0.0","{#OPDATA}":"89.04985520048977"}

As one can see in the attached screenshot of the MIB browser the OID ".1.3.6.1.4.1.55330.2.1" should point to the "operationalTable" which holds all the data.

At first I thought this might be a duplicate of ZBX-15989 but the SNMP entries are laid out differently in my case

Is there an issue with the layout of the entries on the side of the SNMP agent, is the configuration on the ZABBIX server wrong or is this a bug?