-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: Meridian-2015.1.1, 17.0.0
-
Fix Version/s: Meridian-2016.1.7, 21.0.0
-
Component/s: Event Reception - Syslog
-
Security Level: Default (Default Security Scheme)
-
Environment:Any system with the Syslogd service daemon enabled and receiving syslog messages
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
- depends on
-
-
- Resolved
-