Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-4038

translated events are displayed like the original event

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.1
    • Fix Version/s: 1.8.13, 1.9.90, 1.11.0
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Environment:
      Operating System: Linux
      Platform: PC
    • Bugzilla Id:
      4000

      Description

      While translating the nodeDown event (see #3999), I also created a new event definition for a nodeDown event that includes ip Addresses.

      This included %parm[ipaddresses]%.

      However, the new event is displayed just like the original nodeDown event (which was the translation source), so the new parameter is not displayed in the web UI.

      opennms=# select eventuei,eventsource,eventdescr,eventparms from events where eventid in (883123,883124);
      [ RECORD 1 ]-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
      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 ]-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
      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)

      The new event is defined in a custom event file, which is included in eventconf.xml

      shell # tail eventconf.xml
      <event-file>events/hostedpbx.events.xml</event-file>

      <event-file>events/Standard.events.xml</event-file>
      <event-file>events/Translator.default.events.xml</event-file>
      <event-file>events/default.events.xml</event-file>
      </events>

      shell # cat events/hostedpbx.events.xml
      <events>
      <event>
      <uei>uei.opennms.org/intelegence/nodeDownEventWithIpAddresses</uei>
      <event-label>OpenNMS-defined node event: nodeDown</event-label>
      <descr>
      <p>All interfaces on node %nodelabel% 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> <p>IP Addresses: %parm[ipaddresses]%</p>
      </descr>
      <logmsg dest='logndisplay'>
      Node %nodelabel% is down. %parm[eventReason]%
      </logmsg>
      <severity>Major</severity>
      </event>
      </events>

      The event is also not defined anywhere else (I thought maybe it also was auto-generated in the translator file or something):

      1. grep intelegence *
        hostedpbx.events.xml: <uei>uei.opennms.org/intelegence/nodeDownEventWithIpAddresses</uei>

      It would be great if the new event would honor its own event definition.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                agalue Alejandro Galue
                Reporter:
                dk@in-telegence.net Dominik Klein
              • Votes:
                2 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: