Bug 41799 - SyslogAppender should enable to customize Log4j.Level->Syslog.Severity mapping
Summary: SyslogAppender should enable to customize Log4j.Level->Syslog.Severity mapping
Status: NEW
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Appender (show other bugs)
Version: unspecified
Hardware: Other other
: P2 enhancement
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-09 03:17 UTC by Gunter Zeilinger
Modified: 2007-03-09 03:17 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gunter Zeilinger 2007-03-09 03:17:04 UTC
For meeting explicit requirements about used Syslog PRI, not only the used
Syslog Facility, but also the mapping of log4j Levels to Syslog severity values
should be configurable.

E.g. the Audit Trail and Node Authentication (ATNA) profile specified in
Integrating the Healthcare Environment (IHE) IT Infrastructure framework
(http://www.ihe.net/Technical_Framework/index.cfm#IT ) defines:

"The PRI field shall be set using the facility value of 10
(security/authorization messages). Most messages should have the severity value
of 5 (normal but significant), although applications may choose values of 4
(Warning condition) if that is appropriate to the more detailed information in
the audit message."

, which cannot be met with the current hardcoded log4j Levels to Syslog severity
mapping.