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

INFO-severity syslog-derived events end up unmatched

    XMLWordPrintable

Details

    Description

      At some point we refactored Syslogd such that the enum org.opennms.netmgt.syslogd.SyslogSeverity uses the name INFORMATIONAL where it once used INFO. Evidently we forgot to update the event definitions in etc/events/Syslogd.events.xml to match, so now any event created from an INFO-severity syslog message comes out as an unmatched event (i.e. matches the very last event definition in etc/events/default.events.xml)

      Reported by customer in ticket 4245

      Attachments

        Issue Links

          Activity

            People

              jeffg Jeff Gehlbach
              jeffg Jeff Gehlbach
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: