Fixed
Details
Assignee
Jeff GehlbachJeff GehlbachReporter
Jeff GehlbachJeff GehlbachComponents
Affects versions
Priority
Major
Details
Details
Assignee
Jeff Gehlbach
Jeff GehlbachReporter
Jeff Gehlbach
Jeff GehlbachComponents
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created June 16, 2011 at 5:02 PM
Updated January 27, 2017 at 4:19 PM
Resolved June 16, 2011 at 7:14 PM
Currently Syslogd can match syslog messages based on their contents, not on the severity or facility encoded in the PRIO block or the process name. This enhancement makes it possible to match on facility, severity, process name, message contents, or any combination of these. For instance, it will now be possible to catch all "mail.critical" messages from the "postfix/smtpd" process, giving them a UEI like "uei.opennms.org/vendor/postfix/syslog/mail/Critical" rather than the generic "uei.opennms.org/syslog/mail/Critical" that may also apply to messages from dovecot, even without a-priori knowledge of the messages' contents. Among other things, this capability allows for more granular classification of messages for which a specific event definition has not been created.