In the case of SNMPv2 traps, the replacement token %id% currently shows only the enterprise id. For example,sending a ciscoIfExtensionMIBNotifications will yield
Notice that the sub-id 0 is disregarded by OpenNMS. One of our customer's use case is to parse the Log Message field of an event for the full trap oid instead where full trap oid is enterprise id + sub-id + specific id. Many vendors but not all adopt the convention where sub-id = 0. For examples,
Fortigate - https://oidref.com/188.8.131.52.4.1.123184.108.40.206.301
Since OpenNMS %id% token is only displaying the enterprise id and there's no other way to display the full trap id without manually hardcoding most of the event files, customer is not able to make use of parsing the logmsg field as parsing the full trap id is required. It would be helpful for customer if one additional token can be added to distinguish between the more generic %id% token and the more SNMPv2 specific full trap oid token.