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
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
Log4j2 has no concept of receivers, correct?
On Fri, Feb 22, 2013 at 3:39 PM, Ralph Goers ralph.go...@dslextreme.comwrote:
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
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
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
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,
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
I think you are mistaken on the number of Appenders that are missing.
Log4j 2 does have a SocketAppender. It supports both TCP and UDP and accepts a
Layout to allow whatever is sent to be formatted any way you want. The
existing SocketServer expects a serialized event. The XMLLayout could be
