Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <C76B3518F981E0468383F7E091A595B88EF919@c005815.chres1.doleni.net>
References: 
 <CA+ezS6O_=fjkUb2YAWfDuXafH4whcO1LO3qWd8yZda02WkQo3A@mail.gmail.com>
	<C76B3518F981E0468383F7E091A595B88EF914@c005815.chres1.doleni.net>
	<C76B3518F981E0468383F7E091A595B88EF919@c005815.chres1.doleni.net>
Date: Tue, 16 Aug 2011 12:19:41 -0300
Message-ID: 
 <CA+ezS6PG94YX0X6R6=kN2CCqiS8OUxUZMD7rP5vsOEOpB2Dvtg@mail.gmail.com>
Subject: Re: a log4j analyzer
From: Fernando Wermus <fwermus@odeasrl.com.ar>
To: Log4J Users List <log4j-user@logging.apache.org>
Content-Type: multipart/alternative; boundary=90e6ba3fcc31a412f604aaa0e897

--90e6ba3fcc31a412f604aaa0e897
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 <josef.stadelmann@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 bef=
ore
> it eats up cpu cycles.
>
> if ( log.isDebugEnabled() )
> {
>        // Uses many cpu cycles:
>        String fancyLogString =3D buildFancyLogString();
>        // Does nothing because "debug" is currently disabled in
> log4j.properties:
>        log.debug( fancyLogString );
>  }
>
>
>
>
> -----Urspr=FCngliche 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 =3D=3D 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=FCngliche 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
>
>

--90e6ba3fcc31a412f604aaa0e897--