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

Basic syslog messages with Informational severity turn into unknown events

    Details

      Description

      This one's been on my back-burner list for a year.

      In the default case{{,}} syslog messages whose severity is Informational get turned into events for which no event definition exists. The problem is in the SyslogSeverity enum and/or the event definitions in etc/events/Syslogd.events.xml.

      The enum calls severity #6 INFO, so the event objects that come out of Syslogd get a constructed UEI of the form:

      {{uei.opennms.org/syslogd/{facility}/Info}}

      Meanwhile, the event definitions in the config files expect a UEI of the form:

      {{uei.opennms.org/syslogd/{facility}/Info}}rmational

      This disconnect could be fixed in either place, and there are arguments to be made for and against each. Changing the event config file is slightly undesirable, but if changing the enum is considered too risky I'm fine with it since few users are likely to have local edits in this file. We should pick an approach and implement it.

      This problem does not impact events matched in the ueiMatch style.

        Attachments

          Activity

            People

            • Assignee:
              seth@opennms.org Seth Leger (community account)
              Reporter:
              jeffg Jeff Gehlbach
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: