Aaa. I really wish I can edit my issues. Table merged with code after it and I can't fix it 
| Field name | OID prefix | Format |
|---|---|---|
| {#IFNAME} | 1.3.6.1.2.1.31.1.1.1.1 | Unchanged |
| {#SENSOR_VALUE} | 1.3.6.1.4.1.2636.3.60.1.2.1.1.6 | Unchanged |
Current output of "SNMP walk to JSON":
[
{
"{#SNMPINDEX}": "4671.2",
"{#SENSOR_VALUE}": "-209"
},
{
"{#SNMPINDEX}": "4671.1",
"{#SENSOR_VALUE}": "-146"
},
{
"{#SNMPINDEX}": "4671.0",
"{#SENSOR_VALUE}": "-230"
},
{
"{#SNMPINDEX}": "4671",
"{#IFNAME}": "et-8/0/5"
},
{
"{#SNMPINDEX}": "4671.3",
"{#SENSOR_VALUE}": "-265"
}
]
It would be more useful if shorter SNMPINDEX values get expanded and give this:
[
{
"{#SNMPINDEX}": "4671.2",
"{#IFNAME}": "et-8/0/5",
"{#SNMPINDEX_ARRAY}": ["4671", "2"],
"{#SENSOR_VALUE}": "-209"
},
{
"{#SNMPINDEX}": "4671.1",
"{#IFNAME}": "et-8/0/5",
"{#SNMPINDEX_ARRAY}": ["4671", "1"],
"{#SENSOR_VALUE}": "-146"
},
{
"{#SNMPINDEX}": "4671.0",
"{#IFNAME}": "et-8/0/5",
"{#SNMPINDEX_ARRAY}": ["4671", "0"],
"{#SENSOR_VALUE}": "-230"
},
{
"{#SNMPINDEX}": "4671.3",
"{#IFNAME}": "et-8/0/5",
"{#SNMPINDEX_ARRAY}": ["4671", "3"],
"{#SENSOR_VALUE}": "-265"
},
{
"{#SNMPINDEX}": "4671",
"{#IFNAME}": "et-8/0/5",
"{#SNMPINDEX_ARRAY}": ["4671"]
}
]
Losing information that {#IFNAME} came from shorter OID (not {#SNMPINDEX}) is no problem,
because all discovered items need only full {#SNMPINDEX} to get freash monitoring values.
But if this turns out to be needed, I propose adding {#SNMPINDEX_ARRAY} that will have javascript array like [4671.3] instead of text like "4671.3".
Then users can select SNMPINDEX componets they need by JSONpath in LLD Macros tab.
In UI this can work as "expand suffix if needed" checkbox on either on top of "SNMP walk to JSON" step or per each line.
Alternatively it can be "Target SNMPINDEX length" number input on top of "SNMP walk to JSON" if that is easier to implement.
Thank you!
Here is javascript solution
target_depth = 1; // ZBXNEXT-9518 try { var sensors = JSON.parse(value); } catch (e) { throw "Failed to parse JSON of \"SNMP walk to JSON\"."; } byDepth = []; // Sort elements by depth and create SNMPINDEX_ARRAY sensors.forEach(function (element) { index = element['{#SNMPINDEX}']; index_array = index.split('.'); depth = index_array.length; if (byDepth[depth] == null) { byDepth[depth] = {}; } element['{#SNMPINDEX_ARRAY}'] = index_array; byDepth[depth][index] = element; }); result = []; // Go through elements from longest depth to target_depth for(var depth = byDepth.length-1; depth >= target_depth; depth--){ if (byDepth[depth] == null) { continue; } Object.keys(byDepth[depth]).forEach(function (index) { new_element = {}; for(var sub_depth = depth-1, sub_index = index; sub_depth >= 1; sub_depth--){ // Cut away last level from sub_index and merge to new_element sub_index = sub_index.replace(/[.][^.]*$/, "");; if (byDepth[sub_depth] != null) { Object.assign(new_element, byDepth[sub_depth][sub_index]); } } // Merge object itself last for correct SNMPINDEX and SNMPINDEX_ARRAY Object.assign(new_element, byDepth[depth][index]); result.push(new_element); }); } return JSON.stringify(result);
Thank you for this. I've been looking for a way to reference different SNMP tables but have common indices but perhaps one extends further. I'm working to determine if your JS script works in my case.