logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arthur Blake <blake...@yahoo.com>
Subject Re: Logging - What good is it ?
Date Fri, 01 Jun 2007 20:52:10 GMT
JAMon looks like a pretty neat tool.  Almost a full-fledged profiler...
I also noticed it has a lot of cross over with my program log4jdbc (see http://log4jdbc.sourceforge.net)
actually JAmon does a lot more, but it is interesting to see some of your ideas because I
have some similar
ideas for log4jdbc (ability to generically time interfaces, etc.)

Speaking of the Wiki... how does one get a program added on there?  
I tooled around there for a bit and couldn't find any obvious way to add something to the
I would like to get a link to log4jdbc up there...

Arthur Blake

----- Original Message ----
From: Jacob Kjome <hoju@visi.com>
To: Log4J Users List <log4j-user@logging.apache.org>; steve@stevesouza.com
Sent: Thursday, May 31, 2007 2:07:45 PM
Subject: Re: Logging - What good is it ?

Please add a link to JAMon in the Log4j Wiki.  It sounds very useful!



On Thu, 31 May 2007 12:39:29 -0400
  "Steve Souza" <jamonapi@gmail.com> wrote:
> I am the author of the open source monitoring tool JAMon available at
> http://www.jamonapi.com.
> I have just written a log4j appender that passes all log messages through to
> JAMon which allows for a couple nice things to happen.  It will allow you to
> 'tail' your logs in real time and view them from a web page.  This gets
> around the problem of not having access to the log.  JAMon also will allow
> aggregation of log4j messages and Levels (How many times was this log
> message called?  How many times was error called and when was it last
> called?)
> Here is some more info about the appender.  If you haven't used jamon look
> into it as it compliments log4j very nicely.
> 1) With the JAMonAppender you will get summary numbers on how many times the
> log methods of the different levels have been called (i.e.
> DEBUG/WARN/INFO/ERROR/FATAL), and when they were most recently called.  This
> info is viewable in a sortable report in the jamon.war.
> 2) JAMon has buffers that let you via a web page view the last N
> (configurable) log messages that have been sent to the various Levels.  This
> allows you to view the LoggingEvent in a sortable/queriable web page.  This
> works similar to tail in that it doesn't have all rows, but only the most
> recent.  By default this value is set to 100, but it can be increased to
> whatever size is desireable.
> 3) You can count how many times messages of a certain format have been
> called.  For example say you have a message:  Invalid login by 'ssouza'.
> JAMon can generalize this message (Invalid login by ?) and count how many
> times it has been called, and can put the last N of this message type in a
> buffer that will allow you to look at the original detailed message.
> 4) It is easy to use.   No code changes are required.  Simply put
> jamon-2.6.jar in your classpath, install jamon.war, and add the following to
> your log4j property file.
> log4j.rootLogger=DEBUG, jamonAppender
> JAMon log4j.appender.jamonAppender=com.jamonapi.log4j.JAMonAppender
> 5) Note jamon does much more than this.  By using the jamon jdbc driver you
> will have performance metrics on all SQL that goes through your driver.
> Again this requires no code changes and works with all jdbc drivers.
> A live demo is here (version 2.5 so it doesn't have log4j in that release),
> but it does have the jdbc driver.
> http://www.ssouza.com/jamon
> The log4j query screen will look very similar to this most recent N queries
> screen.  Note log4j will also have the entire stacktrace too should the log
> method have been passed it (logger.error("mymessage", exception))
> http://ssouza.kgbinternet.com/jamon/sql.jsp
> Anyone interested can get a prerelease if they email me.  You can also sign
> up at sourceforge to be notified when i make the release.  This release is
> purely a log4j release.  This will be released over the weekend (the code is
> done, just need to come up with a users manual).
> On 5/31/07, Rich Adili <Rich.Adili@xata.com> wrote:
>> I think there's a socket appender available that will allow you to send
>> back to one of your machines. Still some elbow grease required, I
>> imagine.
>> -----Original Message-----
>> From: Propes, Barry L [mailto:barry.l.propes@citi.com]
>> Sent: Thursday, May 31, 2007 10:54 AM
>> To: Log4J Users List
>> Subject: RE: Logging - What good is it ?
>> wow! Your setup sounds worse than mine!
>> I didn't think that was possible!
>> Can those guys share out that ONE directory for you to see?
>> I feel your pain, whereever you are.
>> -----Original Message-----
>> From: Slaughter, Stan [mailto:stan.slaughter@firstdata.com]
>> Sent: Thursday, May 31, 2007 10:39 AM
>> To: log4j-user@logging.apache.org
>> Subject: Logging - What good is it ?
>> We use log4j in a Tomcat web application to log messages to
>> catalina.out.  This works great in development, but in our production
>> system we (the developers) are not allowed access to the catalina.out
>> log file.
>> So, what good is logging debug messages if you can't view the messages
>> when you need to the most, like when the app crashes in production ?
>> (yes - it makes no sense to me either).
>> Hence, my question: What is the most straight forward way to view the
>> log file remotely ?
>> I have no idea (and no control) on what the remote production servers
>> name will be, but I do know the url so I am looking for a web based
>> answere.  Something with the minimum functionality of 'tail -f
>> catalina.out' would do.
>> Can Chainsaw be configured in some way?
>> Can log4j be modified to broadcast to a specific port on a web server?
>> Any third party viewers - aka - like a Lambda Probe 'lite'?   One that
>> just allows for log file viewing.  My boss-people will not allow Lambda
>> Probe to be installed in production as it allows too much control (ie
>> developer grunts should not be able to stop/start the tomcat instances
>> in production).
>> P.S.
>> Do to internal departmental structuring/politics and development costs;
>> logging to a database is not an option.
>> Stan Slaughter
>> -----------------------------------------
>> The information in this message may be proprietary and/or
>> confidential, and protected from disclosure.  If the reader of this
>> message is not the intended recipient, or an employee or agent
>> responsible for delivering this message to the intended recipient,
>> you are hereby notified that any dissemination, distribution or
>> copying of this communication is strictly prohibited. If you have
>> received this communication in error, please notify First Data
>> immediately by replying to this message and deleting it from your
>> computer.
>> ---------------------------------------------------------------------
>> 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

Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers
- Check it out.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message