You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Paul Duffy <pa...@cisco.com> on 2007/08/28 23:05:42 UTC
Centralized logging for distributed loggers.
Folks,
My team is investigating Log4j's ability to direct many server's logging
data to a single/central server for presentation and analysis. Been
looking at Socket and JMSAppenders, etc.
What products exists in OSS land or commercial which are fully featured,
centralized log4J listeners? Essentially we seek...
- ability to direct many "client" loggers to central location
- central server collates the logging streams via time stamp, etc.
- some level of sophisticated GUI to assist interpretation, filtering of
the logging data.
- BONUS: allow centralized configuration of the distributed logging clients.
- etc.
Is ChainSaw what we should be looking at? Others?
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Centralized logging for distributed loggers.
Posted by Jacob Kjome <ho...@visi.com>.
At 02:03 PM 9/20/2007, you wrote:
>Any reason ChainSaw has been dropped from the list referenced below?
>
I guess I thought of that page as external resources while Chainsaw
is part of Log4j proper. But the page could certainly have a
different slant. Maybe one section for external resources and
another for official Log4j resources. Or maybe drop the distinction
altogether. If you are concerned about it, I encourage you to edit
it to your liking. The the Wiki is for the community, not just for
Log4j committers.
Jake
>Jacob Kjome wrote:
>> At 04:08 PM 8/28/2007, you wrote:
>> >For gui with filtering look at chainsaw I recommend. You would have to
>> >extend it a little but it is a good start. V1.3+ has a better gui tool
>> >as well
>> >
>>
>> I'm not clear on exactly what version number will be used for the
>> release of the next version of Chainsaw. Just to be clear, though, if
>> you are referring to "1.3" as the next version of Log4j, please note
>> that development of 1.3 has been discontinued in favor of continued
>> development of Log4j 1.2.xx. A separate "extras" library will be
>> released that will contain select features originally developed as
>> part of the now dead 1.3 codebase, but will be compatible with Log4j
>> 1.2.xx.
>>
>> Now, to Paul's question on centralized logging. Perhaps one of the
>> projects listed in the wiki will do what you need? This is not an
>> exhaustive list, and I encourage others to add to it.
>>
>> http://wiki.apache.org/logging-log4j/Log4jRelatedResources
>>
>>
>> Jake
>>
>> >-----Original Message-----
>> >From: Paul Duffy [mailto:paduffy@cisco.com]
>> >Sent: Tuesday, August 28, 2007 4:06 PM
>> >To: Log4J Users List
>> >Subject: Centralized logging for distributed loggers.
>> >
>> >Folks,
>> >
>> >My team is investigating Log4j's ability to direct many server's logging
>> >data to a single/central server for presentation and analysis. Been
>> >looking at Socket and JMSAppenders, etc.
>> >
>> >What products exists in OSS land or commercial which are fully featured,
>> >centralized log4J listeners? Essentially we seek...
>> >
>> >- ability to direct many "client" loggers to central location
>> >- central server collates the logging streams via time stamp, etc.
>> >- some level of sophisticated GUI to assist interpretation, filtering of
>> >the logging data.
>> >- BONUS: allow centralized configuration of the distributed logging
>> >clients.
>> >- etc.
>> >
>> >Is ChainSaw what we should be looking at? Others?
>> >
>> >Cheers
>> >
>> >
>> >
>> >---------------------------------------------------------------------
>> >To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> >For additional commands, e-mail: log4j-user-help@logging.apache.org
>> >
>> >
>> >---------------------------------------------------------------------
>> >To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> >For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Centralized logging for distributed loggers.
Posted by Paul Duffy <pa...@cisco.com>.
Any reason ChainSaw has been dropped from the list referenced below?
Jacob Kjome wrote:
> At 04:08 PM 8/28/2007, you wrote:
> >For gui with filtering look at chainsaw I recommend. You would have to
> >extend it a little but it is a good start. V1.3+ has a better gui tool
> >as well
> >
>
> I'm not clear on exactly what version number will be used for the
> release of the next version of Chainsaw. Just to be clear, though, if
> you are referring to "1.3" as the next version of Log4j, please note
> that development of 1.3 has been discontinued in favor of continued
> development of Log4j 1.2.xx. A separate "extras" library will be
> released that will contain select features originally developed as
> part of the now dead 1.3 codebase, but will be compatible with Log4j
> 1.2.xx.
>
> Now, to Paul's question on centralized logging. Perhaps one of the
> projects listed in the wiki will do what you need? This is not an
> exhaustive list, and I encourage others to add to it.
>
> http://wiki.apache.org/logging-log4j/Log4jRelatedResources
>
>
> Jake
>
> >-----Original Message-----
> >From: Paul Duffy [mailto:paduffy@cisco.com]
> >Sent: Tuesday, August 28, 2007 4:06 PM
> >To: Log4J Users List
> >Subject: Centralized logging for distributed loggers.
> >
> >Folks,
> >
> >My team is investigating Log4j's ability to direct many server's logging
> >data to a single/central server for presentation and analysis. Been
> >looking at Socket and JMSAppenders, etc.
> >
> >What products exists in OSS land or commercial which are fully featured,
> >centralized log4J listeners? Essentially we seek...
> >
> >- ability to direct many "client" loggers to central location
> >- central server collates the logging streams via time stamp, etc.
> >- some level of sophisticated GUI to assist interpretation, filtering of
> >the logging data.
> >- BONUS: allow centralized configuration of the distributed logging
> >clients.
> >- etc.
> >
> >Is ChainSaw what we should be looking at? Others?
> >
> >Cheers
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >For additional commands, e-mail: log4j-user-help@logging.apache.org
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> >For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Centralized logging for distributed loggers.
Posted by Paul Smith <ps...@aconex.com>.
> >Folks,
> >
> >My team is investigating Log4j's ability to direct many server's
> logging
> >data to a single/central server for presentation and analysis. Been
> >looking at Socket and JMSAppenders, etc.
> >
> >What products exists in OSS land or commercial which are fully
> featured,
> >centralized log4J listeners? Essentially we seek...
> >
> >- ability to direct many "client" loggers to central location
> >- central server collates the logging streams via time stamp, etc.
> >- some level of sophisticated GUI to assist interpretation,
> filtering of
> >the logging data.
> >- BONUS: allow centralized configuration of the distributed logging
> >clients.
> >- etc.
> >
> >Is ChainSaw what we should be looking at? Others?
Chainsaw can definitely do these things, but you need to have the GUI
running to capture the data. There's no reason you can't build an
extremely simply application that wraps up a set of configured
Receivers and appenders to centralise all logging events to one host.
This is also why I started the Pinpoint project:
http://svn.apache.org/repos/asf/labs/pinpoint/
It's designed to be a central logging repository for logging analysis.
It's not even close to production ready, but steadily working towards
it. The goal I have to use this in our production systems is to have
a centralised logging server that all hosts send their events to (via
socket or jms). Pinpoint indexes these events and provides a rolling
set of daily context zones to perform searches on.
I'm leveraging the richness of Lucene's indexing and searching
infrastructure and hope to provide an extremely powerful log
correlation tool that utilises log4j's inbuilt context mechanisms (by
Thread, by MDC/NDC values etc). Currently there's only a Command-
line tool and a basic Service module but a web-based interface is on
the way.
This is inspired by the commercial Splunk application (which I
haven't tried personally, just read about what they're trying to
achieve). I'm hoping to provide a much better and free alternative! :)
cheers,
Paul Smith
RE: Centralized logging for distributed loggers.
Posted by Jacob Kjome <ho...@visi.com>.
At 04:08 PM 8/28/2007, you wrote:
>For gui with filtering look at chainsaw I recommend. You would have to
>extend it a little but it is a good start. V1.3+ has a better gui tool
>as well
>
I'm not clear on exactly what version number will be used for the
release of the next version of Chainsaw. Just to be clear, though,
if you are referring to "1.3" as the next version of Log4j, please
note that development of 1.3 has been discontinued in favor of
continued development of Log4j 1.2.xx. A separate "extras" library
will be released that will contain select features originally
developed as part of the now dead 1.3 codebase, but will be
compatible with Log4j 1.2.xx.
Now, to Paul's question on centralized logging. Perhaps one of the
projects listed in the wiki will do what you need? This is not an
exhaustive list, and I encourage others to add to it.
http://wiki.apache.org/logging-log4j/Log4jRelatedResources
Jake
>-----Original Message-----
>From: Paul Duffy [mailto:paduffy@cisco.com]
>Sent: Tuesday, August 28, 2007 4:06 PM
>To: Log4J Users List
>Subject: Centralized logging for distributed loggers.
>
>Folks,
>
>My team is investigating Log4j's ability to direct many server's logging
>data to a single/central server for presentation and analysis. Been
>looking at Socket and JMSAppenders, etc.
>
>What products exists in OSS land or commercial which are fully featured,
>centralized log4J listeners? Essentially we seek...
>
>- ability to direct many "client" loggers to central location
>- central server collates the logging streams via time stamp, etc.
>- some level of sophisticated GUI to assist interpretation, filtering of
>the logging data.
>- BONUS: allow centralized configuration of the distributed logging
>clients.
>- etc.
>
>Is ChainSaw what we should be looking at? Others?
>
>Cheers
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>For additional commands, e-mail: log4j-user-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
RE: Centralized logging for distributed loggers.
Posted by "Harp, George" <GH...@GAINSystems.com>.
For gui with filtering look at chainsaw I recommend. You would have to
extend it a little but it is a good start. V1.3+ has a better gui tool
as well
-----Original Message-----
From: Paul Duffy [mailto:paduffy@cisco.com]
Sent: Tuesday, August 28, 2007 4:06 PM
To: Log4J Users List
Subject: Centralized logging for distributed loggers.
Folks,
My team is investigating Log4j's ability to direct many server's logging
data to a single/central server for presentation and analysis. Been
looking at Socket and JMSAppenders, etc.
What products exists in OSS land or commercial which are fully featured,
centralized log4J listeners? Essentially we seek...
- ability to direct many "client" loggers to central location
- central server collates the logging streams via time stamp, etc.
- some level of sophisticated GUI to assist interpretation, filtering of
the logging data.
- BONUS: allow centralized configuration of the distributed logging
clients.
- etc.
Is ChainSaw what we should be looking at? Others?
Cheers
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org