Clint Combs has announced the release of LogFeeder 1.0, a Swing client application that listens for logging events from java.util.logging on a socket. As the application's home page says, it's not complete yet (despite the 1.0 release number), but might be of use for people who leverage the built-in logging Java libraries for logging.
Configuring java.util.logging for the use of LogFeeder is pretty easy. However, one caveat is that setting up j.u.l to use the SocketHandler means you're going to want to have an instance of LogFeeder running - otherwise, initialization of the Logger will throw an exception. (Possibly this is a candidate for a future enhancement of LogFeeder or j.u.l itself.)
-
LogFeeder 1.0, for viewing java.util.logging output (6 messages)
- Posted by: Joseph Ottinger
- Posted on: May 05 2006 07:23 EDT
Threaded Messages (6)
- LogFeeder 1.0, for viewing java.util.logging output by Neil Bartlett on May 05 2006 08:26 EDT
- LogFeeder 1.0, for viewing java.util.logging output by Joseph Ottinger on May 05 2006 08:38 EDT
- LogFeeder 1.0, for viewing java.util.logging output by Fabrizio Gianneschi on May 05 2006 08:47 EDT
- LogFeeder 1.0, for viewing java.util.logging output by Calum Shaw-Mackay on May 05 2006 09:17 EDT
- SMTPHandler for java.util.logging by Sean Sullivan on May 05 2006 14:31 EDT
- LogFeeder 1.0, for viewing java.util.logging output by Arik Kfir on May 06 2006 07:57 EDT
-
LogFeeder 1.0, for viewing java.util.logging output[ Go to top ]
- Posted by: Neil Bartlett
- Posted on: May 05 2006 08:26 EDT
- in response to Joseph Ottinger
What about security? Log messages often contain sensitive information... if I make them available over a socket, who else might connect? -
LogFeeder 1.0, for viewing java.util.logging output[ Go to top ]
- Posted by: Joseph Ottinger
- Posted on: May 05 2006 08:38 EDT
- in response to Neil Bartlett
What about security? Log messages often contain sensitive information... if I make them available over a socket, who else might connect?
Obviously, security isn't a huge deal here, and it'd be easy enough to create a Handler that did take security into account, although that'd be invasive for the runtime. -
LogFeeder 1.0, for viewing java.util.logging output[ Go to top ]
- Posted by: Fabrizio Gianneschi
- Posted on: May 05 2006 08:47 EDT
- in response to Joseph Ottinger
Also che Chainsaw project has similar features and the socket option. It's easy to log both Log4J and util.logging sources.
http://logging.apache.org/log4j/docs/chainsaw.html -
LogFeeder 1.0, for viewing java.util.logging output[ Go to top ]
- Posted by: Calum Shaw-Mackay
- Posted on: May 05 2006 09:17 EDT
- in response to Fabrizio Gianneschi
Eros does a similar thing but provides a Jini service as a logging handler and places the log messages into a database, which can then be queried. Version 1.0 will be released in the next few days - http://eros.jini.org ( or the new site (when approved @ http://eros.dev.java.net )
--Calum -
SMTPHandler for java.util.logging[ Go to top ]
- Posted by: Sean Sullivan
- Posted on: May 05 2006 14:31 EDT
- in response to Joseph Ottinger
I ported Log4j's SMTPAppender to java.util.logging.
The project is known as SMTPHandler:
http://smtphandler.sourceforge.net/ -
LogFeeder 1.0, for viewing java.util.logging output[ Go to top ]
- Posted by: Arik Kfir
- Posted on: May 06 2006 07:57 EDT
- in response to Joseph Ottinger
Does anyone really use the java.util.logging package?? I mean, levels like fine, finer, finest...what were they thinking? Why can't I just do "log.debug(..)". I'm sticking to log4j...