I see, that since opennms-19, openNMS is processing events differently. When we have different event definitions (different id, generic, specific and/or varbind) with the same UEI, then openNMS presents event, that is first on the list and not that one that matches exact definition. Before opennms-19 I was able to send different traps, that were creating events(alarms) with the same UEI, but with different severity. Now, it is not possible, because openNMS presents always the same event - the first one on the configuration list.
Is it a BUG or a some feature?