[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4net-dev
Subject:    [jira] Created: (LOG4NET-262) Redesigning Syslog in Log4net
From:       "Antonio Anzivino (JIRA)" <jira () apache ! org>
Date:       2010-07-06 21:43:49
Message-ID: 2389310.224181278452629779.JavaMail.jira () thor
[Download RAW message or body]

Redesigning Syslog in Log4net
-----------------------------

                 Key: LOG4NET-262
                 URL: https://issues.apache.org/jira/browse/LOG4NET-262
             Project: Log4net
          Issue Type: New Feature
          Components: Appenders
    Affects Versions: 1.2.10
         Environment: All
            Reporter: Antonio Anzivino
            Priority: Minor


Hello,
I just want to sugges to apply the following modifications to Log4net (apply also to \
Log4j):

*Create a SyslogLayout layout class that formats messages into Syslog format (both \
RFC3164 and RFC5424). Currently you have to search for a good PatternLayout that \
matches RFC specifications. Even if that could be, ultimately, inheriting from \
PatternLayout and setting a constant pattern... At least we have a valid layout in a \
                class
*RemoteSyslogAppender currently prepends the PriVal field to the regular message \
formatted accordingly with the pattern. SimpleLayout might not work properly. \
Suggesting to make RemoteSyslogAppender work only with properly implemented \
SyslogLayout[s] for both the RFCs

Having a Syslog layout, especially for RFC5424 which is not only recent, but supports \
a full UTC timestamp complete with year (unsupported by RFC3164) is very useful when \
performing long-term log analysis and allows to store messages in Syslog format into \
files, almost like syslog-ng daemon does with /var/log/messages.

I'm currently working on an open source logging framework (Logbus-ng) that does only \
log collection and broadcasting and *that we want to make fully compatible with \
Log4xxx*: our team has already implemented a fully working formatter for Syslog \
RFC5424 messages. If you need code, we can share it. I personally plan to implement \
these two features as classes external to Log4net, but I would like to suggest the \
Log4net dev team to do so before us because I feel the utility of such a work for the \
community.

Thank you.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[prev in list] [next in list] [prev in thread] [next in thread]