The solution has been verified on branch 1.8

Cherry-picked on revision 882f24cfe734efae0773554e14cf18af71227b41 for 1.8

Dominik is right. The problem is related only with the event's description.

The solution is just add the following line on the method cloneEvent:
clonedEvent.setDescr(null);

Committed into revision 1e72378add9fd64d8672f307926219371e2ccfaf for 1.10.

On my experiments, with Cisco version for SNMP_Link_Down and SNMP_Link_Up, defined on Cisco.events.xml, the problem affects both, description and logmessage.

My first attempt shows me a more critical error: if I set the original event as "donotpersist", the translated event won't be persisted because it has the same logmessage. So I let both as "logndisplay".

I applied a simple patch:

diff --git a/opennms-services/src/main/java/org/opennms/netmgt/config/EventTranslatorConfigFactory.java b/opennms-services/src/main/java/org/opennms/netmgt/config/
index 88432c4..3bf1305 100644
— a/opennms-services/src/main/java/org/opennms/netmgt/config/EventTranslatorConfigFactory.java
+++ b/opennms-services/src/main/java/org/opennms/netmgt/config/EventTranslatorConfigFactory.java
@@ -446,6 +446,8 @@ public final class EventTranslatorConfigFactory implements EventTranslatorConfig

• eventd using the data from eventconf, we unset it here to eventd

• can reset to the proper new settings.
  */
  + clonedEvent.setLogmsg(null); // Fix for bugs 4000 and 4017
  + clonedEvent.setDescr(null); // Fix for bugs 4000 and 4017
  clonedEvent.setAlarmData(null);
  clonedEvent.setSeverity(null);
  return clonedEvent;

The patch make sense because of the explanation of why setAlarmData and setSeverity are set to null.

After restart with the new jar, the event page now shows logmessage and description as expected.

BUT if I mark again the original message as "donotpersist", it is still persisted, and I don't know why.

Maybe the patch is not correct, or I am missing something.

Any thoughts?

•  

  •  

    • has been marked as a duplicate of this bug. ***

Interestingly, this does not seem to be true for the event label (eventlogmsg in the DB). But the description is not taken from the actual event's definition, but from the original event's definition.

opennms=# select eventlogmsg,eventuei,eventsource,eventdescr,eventparms from events where eventid in (883123,883124);
[ RECORD 1 ]------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- eventlogmsg | Node is down.
eventuei | uei.opennms.org/nodes/nodeDown
eventsource | OpenNMS.Poller.DefaultPollContext
eventdescr | <p>All interfaces on node are down.</p> <p>This event is generated when node outage processing determines that all interfaces on the node are down.</p> <p>New outage records have been created and service level availability calculations will be impacted until this outage is resolved.</p>
eventparms |
[ RECORD 2 ]------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- eventlogmsg | Node zzz dk test is down.
eventuei | uei.opennms.org/intelegence/nodeDownEventWithIpAddresses
eventsource | OpenNMS.EventTranslator
eventdescr | <p>All interfaces on node are down.</p> <p>This event is generated when node outage processing determines that all interfaces on the node are down.</p> <p>New outage records have been created and service level availability calculations will be impacted until this outage is resolved.</p>
eventparms | ipaddresses={1.1.1.1,2.2.2.2,3.3.3.3,4.4.4.4,5.5.5.5}(string,text)