I forgot the two main socket appenders of course:
SocketAppender -> SocketReceiver
SocketHubAppender -> SocketHubReceiver (allow reverse-connects from the
'receiver' to the 'appender')


On Fri, Feb 22, 2013 at 4:51 PM, Scott Deboy <scott.de...@gmail.com> wrote:

> There are quite a few appenders and associated receivers in log4j 1.x.
>  Most of these appenders and all of these receivers are missing in log4j2:
>
> MulticastAppender->MulticastReceiver
> UDPAppender and non-log4j appenders which support generating events over
> UDP which conform to log4j's dtd (log4net, etc)->UDPReceiver
> *FileAppender with a regular text layout->(VFS)LogFilePatternReceiver
> *FileAppender with an xml layout->LogFileXMLReceiver
> non-log4j appenders which support generating events over TCP which conform
> to log4j's dtd (log4perl, etc)->XMLSocketReceiver
> JMSAppender->JMSReceiver
> DBAppender->DBReceiver (DBAppender uses a predefined schema)
> Custom DB definition->CustomSQLDBReceiver
>
> There may be others, those are the ones I can remember off the top of my
> head.
>
> Scott
>
>
> On Fri, Feb 22, 2013 at 4:44 PM, Scott Deboy <scott.de...@gmail.com>wrote:
>
>> In log4j1.x, yes, receivers can be configured via the 'plugin' element in
>> log4j.xml and eventually end up appending received events to the local
>> log4j system, which are then picked up by locally defined appenders.  This
>> is how Chainsaw works - it programmatically registers its own appender to
>> pull in events appended by the configured receivers.
>>
>>
>>
>>
>>
>> On Fri, Feb 22, 2013 at 4:37 PM, Ralph Goers 
>> <ralph.go...@dslextreme.com>wrote:
>>
>>> Not in the configuration as yet.   However, I've implemented a couple of
>>> "servers" that are independent "main programs" that can receive log events.
>>>  I am assuming that the main difference is that the receiver would not be a
>>> main but would be embedded in the application.
>>>
>>> Where are they documented?
>>>
>>> Ralph
>>>
>>>
>>> On Feb 22, 2013, at 3:51 PM, Scott Deboy wrote:
>>>
>>> > Log4j2 has no concept of receivers, correct?
>>> >
>>> >
>>> > On Fri, Feb 22, 2013 at 3:39 PM, Ralph Goers <
>>> ralph.go...@dslextreme.com>wrote:
>>> >
>>> >> Scott,
>>> >>
>>> >> Yogi has been asking other questions about Log4j 2 so I'm not clear
>>> if his
>>> >> question applies to that or 1.x.  Or does the
>>> VFSLogFilePatternReceiver
>>> >> work with Log4j 2?
>>> >>
>>> >> Ralph
>>> >>
>>> >>
>>> >> On Feb 22, 2013, at 3:32 PM, Scott Deboy wrote:
>>> >>
>>> >>> If you want the events to end up in log4j (being processed by an
>>> >> appender,
>>> >>> it's very easy, just define a (VFS)LogFilePatternReceiver in your
>>> log4j
>>> >>> configuration file.
>>> >>>
>>> >>> If you instead want the LogEvents so you can do something else with
>>> them,
>>> >>> you can use the (VFS)LogFilePatternReceiver outside of log4j, just
>>> >>> construct it, call appropriate setters, and call activateOptions.
>>> >> Wherever
>>> >>> the receiver calls doPost, you can instead hold on to the generated
>>> >> event.
>>> >>>
>>> >>>
>>> >>
>>> http://svn.apache.org/repos/asf/logging/chainsaw/trunk/src/main/java/org/apache/log4j/varia/LogFilePatternReceiver.java
>>> >>>
>>> >>> The VFS version supports Commons-VFS sources (sftp, etc):
>>> >>>
>>> >>
>>> http://svn.apache.org/repos/asf/logging/chainsaw/trunk/src/main/java/org/apache/log4j/chainsaw/vfs/VFSLogFilePatternReceiver.java
>>> >>>
>>> >>> Scott
>>> >>>
>>> >>>
>>> >>> On Fri, Feb 22, 2013 at 2:23 PM, Yogi Nerella <ynerella...@gmail.com
>>> >
>>> >> wrote:
>>> >>>
>>> >>>> Hi,
>>> >>>>
>>> >>>> Any tools which can take a log file and the pattern string and
>>> generate
>>> >> the
>>> >>>> events?
>>> >>>>
>>> >>>> Thanks
>>> >>>> Yogi
>>> >>>>
>>> >>
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
>>> >> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>>> >>
>>> >>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
>>> For additional commands, e-mail: log4j-user-h...@logging.apache.org
>>>
>>>
>>
>

Reply via email to