Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

INFO-severity syslog-derived events end up unmatched

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

Environment

Any system with the Syslogd service daemon enabled and receiving syslog messages

Acceptance / Success Criteria

None

depends on

Lucidchart Diagrams

Activity

Show:

Seth Leger September 7, 2017 at 3:24 PM

This bugfix was nullified by the changes in so informational messages are still broken in Meridian 2016.1.6 and Horizon 20 and lower. I'm adjusting the fix versions to reflect versions where you will see proper behavior.

Note that Meridian 2015 will work properly but will use the "Info" UEI.

Jeff Gehlbach February 4, 2016 at 9:13 AM

Fixed!

Jeff Gehlbach February 4, 2016 at 9:07 AM

CI passed. Secondary pull request created and merged against foundation-2016:

https://github.com/OpenNMS/opennms/pull/573

Jeff Gehlbach February 3, 2016 at 5:37 PM

Created and merged pull request:

https://github.com/OpenNMS/opennms/pull/567

Waiting on CI.

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created February 3, 2016 at 3:34 PM
Updated September 20, 2017 at 3:29 PM
Resolved February 4, 2016 at 9:13 AM