A feature for tokenizing/splitting of the parm varbind value similar to one available on varbind name would be of high value.
The most similar feature described now in Event Substitutions wiki page is parm name tokenizing which is mostly used with IP equipment like for instance bgpBackwardTransition alarms or other alarms in which the alarmed object is reported in OID index, and not in a varbind value.
This is useful on network elements which we can't modify the SNMP trap varbind text and which string is splitted by some character. Full text becomes unclear for users and would require tokens to be defined for information clearness and alarm reduction string.
e.g.
string below is a single string varbind value from a legacy equipment from which we would only require to get split the content "INSH01" "HARD" "$HN3L8" and ignore the rest of content, being that part of the content had to be included in alarm reduction key.
A feature for tokenizing/splitting of the parm varbind value similar to one available on varbind name would be of high value.
The most similar feature described now in Event Substitutions wiki page is parm name tokenizing which is mostly used with IP equipment like for instance bgpBackwardTransition alarms or other alarms in which the alarmed object is reported in OID index, and not in a varbind value.
https://wiki.opennms.org/wiki/Event_substitutions
Sintax could be something like:
%parm[value-#<num><sep><token-num>]%
This is useful on network elements which we can't modify the SNMP trap varbind text and which string is splitted by some character. Full text becomes unclear for users and would require tokens to be defined for information clearness and alarm reduction string.
e.g.
string below is a single string varbind value from a legacy equipment from which we would only require to get split the content "INSH01" "HARD" "$HN3L8" and ignore the rest of content, being that part of the content had to be included in alarm reduction key.
INSH01 2018-10-09 02:13:45 SOFT 5257 $HN3L8 001 33 20 24350
INSH01 2018-10-09 03:15:45 HARD 5257 $HN3L8 001 33 20 24350
Alarm Reduction Key would become like below ignoring the timestamp and SOFT/HARD indication from node, as well as remaining attributes.
%uei%:%snmphost%:%parm[value-#3 1]%:%parm[value-#3 6]%