> I don't see why the log shouldn't be able to store similar information.
Depending on where you live, logging such information may be an illegal act
(breach of Data Protection, data misuse) or breaking of industry regulations
(e.g. recording the 3 security digits from the back of a credit card).
>if(logger.isDebugEnabled()) {
> logger.debug("Entry number: " + i + " is " + String.valueOf(entry[i])); }
>Personally, I think that is an absolute abomination, and a major failure
>of the logging framework / Java combination.
It certainly makes the code ugly. If I am going to use an "isDebugEna
>3. Best practices should include use of NDC.
Now, here's a question. Why NDC rather than MDC? And how do you decide
when one is more appropriate than the other?
J.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addition
Hi Julius,
I asked about best practice a while back, so it's good to see this come up
again as I am still trying to get and idea on what "best practice" is with
regards to logging.
I agree with avoiding multiple-lines, but there are occasions where this
simply isn't possible. These should really
eeing too
much stuff logged at too high a priority. If your log contains 10%
ERRORs people grow numb and don't take things seriously.
Cheers, Eric
-Original Message-
From: Jason Irwin [mailto:[EMAIL PROTECTED]
Sent: Friday, February 29, 2008 1:38 AM
To: log4j-user@logging.apache
I've been doing a fair bit of trawling around logging for some best practice
on logging. Does anyone know of a good resource? Or a book which goes into
detail on this?
The levels FATAL and ERROR are pretty self-explanatory. Are there rules of
thumb for INFO, WARN, DEBUG and TRACE?
Common me
>I'm not sure about the MDC, but the LocationInfo was known to be
>affected by serialization incompatibility between the log4j 1.2 and
>1.3 alphas. The Chainsaw currently available on the WebStart is built
>on a log4j 1.3 alpha and will lose information when connected to a
>log4j 1.2 sourc
I just started using Chainsaw the other day. It seems like a great addition
to Log4j and I hope the effort to improve it continues.
I've been playing with the zero-conf stuff, but try as I might I cannot get
at the location info or MDC data over this (it's find when reading an XML
log file).
I
