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 Fernando Wermus <fw...@odeasrl.com.ar> on 2011/08/10 20:24:57 UTC

a log4j analyzer

Hi all,
   We are facing some performance problems and we would like to use a tool
to analyze our logs to make a point. Which is your experience about it?

thanks in advance

AW: a log4j analyzer

Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
I would suggest to use a JDBC- or any other log4j-suitable-DB-Appender, 
then have the log-events as entries in the real DB 
then use a DB based analysis tools to do the actual analysis.
And you should start writing down your requirements first.
Josef

 

-----Ursprüngliche Nachricht-----
Von: Fernando Wermus [mailto:fwermus@odeasrl.com.ar] 
Gesendet: Dienstag, 16. August 2011 17:20
An: Log4J Users List
Betreff: Re: a log4j analyzer

Josef Stadelmann,
        First of all thanks for replying. What we need is the best tool for
analyzing logs file. We haven't found a good tool yet.

thanks in advance

2011/8/15 Stadelmann Josef <jo...@axa-winterthur.ch>

> This approach will also help to speed logging up. Given you intend to log a
> debug event, then test it as shown and only go through the lengthy cycles if
> debug logging is in fact enabled That approach checks a boolean first before
> it eats up cpu cycles.
>
> if ( log.isDebugEnabled() )
> {
>        // Uses many cpu cycles:
>        String fancyLogString = buildFancyLogString();
>        // Does nothing because "debug" is currently disabled in
> log4j.properties:
>        log.debug( fancyLogString );
>  }
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
> Gesendet: Donnerstag, 11. August 2011 09:57
> An: Log4J Users List
> Betreff: AW: a log4j analyzer
>
> How do you measure?
> What is he difference between
>
> Raising the log level to fatal == no logging if that application runs
> Raising the log level to info
> Raising the log level to debug or trace or all
>
> What is the time difference you see under your setup which we don't know.
>
> Josef
> Alias Sepp
>
> -----Ursprüngliche Nachricht-----
> Von: Fernando Wermus [mailto:fwermus@odeasrl.com.ar]
> Gesendet: Mittwoch, 10. August 2011 20:25
> An: log4j-user@logging.apache.org
> Betreff: a log4j analyzer
>
> Hi all,
>   We are facing some performance problems and we would like to use a tool
> to analyze our logs to make a point. Which is your experience about it?
>
> thanks in advance
>
> ---------------------------------------------------------------------
> 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: a log4j analyzer

Posted by Fernando Wermus <fw...@odeasrl.com.ar>.
Josef Stadelmann,
        First of all thanks for replying. What we need is the best tool for
analyzing logs file. We haven't found a good tool yet.

thanks in advance

2011/8/15 Stadelmann Josef <jo...@axa-winterthur.ch>

> This approach will also help to speed logging up. Given you intend to log a
> debug event, then test it as shown and only go through the lengthy cycles if
> debug logging is in fact enabled That approach checks a boolean first before
> it eats up cpu cycles.
>
> if ( log.isDebugEnabled() )
> {
>        // Uses many cpu cycles:
>        String fancyLogString = buildFancyLogString();
>        // Does nothing because "debug" is currently disabled in
> log4j.properties:
>        log.debug( fancyLogString );
>  }
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch]
> Gesendet: Donnerstag, 11. August 2011 09:57
> An: Log4J Users List
> Betreff: AW: a log4j analyzer
>
> How do you measure?
> What is he difference between
>
> Raising the log level to fatal == no logging if that application runs
> Raising the log level to info
> Raising the log level to debug or trace or all
>
> What is the time difference you see under your setup which we don't know.
>
> Josef
> Alias Sepp
>
> -----Ursprüngliche Nachricht-----
> Von: Fernando Wermus [mailto:fwermus@odeasrl.com.ar]
> Gesendet: Mittwoch, 10. August 2011 20:25
> An: log4j-user@logging.apache.org
> Betreff: a log4j analyzer
>
> Hi all,
>   We are facing some performance problems and we would like to use a tool
> to analyze our logs to make a point. Which is your experience about it?
>
> thanks in advance
>
> ---------------------------------------------------------------------
> 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
>
>

AW: a log4j analyzer

Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
This approach will also help to speed logging up. Given you intend to log a debug event, then test it as shown and only go through the lengthy cycles if debug logging is in fact enabled That approach checks a boolean first before it eats up cpu cycles.

if ( log.isDebugEnabled() ) 
{ 	
	// Uses many cpu cycles: 
	String fancyLogString = buildFancyLogString(); 
	// Does nothing because "debug" is currently disabled in log4j.properties: 
	log.debug( fancyLogString );
 }




-----Ursprüngliche Nachricht-----
Von: Stadelmann Josef [mailto:josef.stadelmann@axa-winterthur.ch] 
Gesendet: Donnerstag, 11. August 2011 09:57
An: Log4J Users List
Betreff: AW: a log4j analyzer

How do you measure?
What is he difference between

Raising the log level to fatal == no logging if that application runs
Raising the log level to info
Raising the log level to debug or trace or all

What is the time difference you see under your setup which we don't know.

Josef
Alias Sepp

-----Ursprüngliche Nachricht-----
Von: Fernando Wermus [mailto:fwermus@odeasrl.com.ar] 
Gesendet: Mittwoch, 10. August 2011 20:25
An: log4j-user@logging.apache.org
Betreff: a log4j analyzer

Hi all,
   We are facing some performance problems and we would like to use a tool
to analyze our logs to make a point. Which is your experience about it?

thanks in advance

---------------------------------------------------------------------
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

AW: a log4j analyzer

Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
How do you measure?
What is he difference between

Raising the log level to fatal == no logging if that application runs
Raising the log level to info
Raising the log level to debug or trace or all

What is the time difference you see under your setup which we don't know.

Josef
Alias Sepp

-----Ursprüngliche Nachricht-----
Von: Fernando Wermus [mailto:fwermus@odeasrl.com.ar] 
Gesendet: Mittwoch, 10. August 2011 20:25
An: log4j-user@logging.apache.org
Betreff: a log4j analyzer

Hi all,
   We are facing some performance problems and we would like to use a tool
to analyze our logs to make a point. Which is your experience about it?

thanks in advance

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org