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 (herse.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <45641758.8040005@gmail.com>
References: <45641758.8040005@gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <52E701B6-CF2C-4342-A029-D1140203C101@apache.org>
Content-Transfer-Encoding: 7bit
From: Curt Arnold <carnold@apache.org>
Subject: Re: Trace and Debug level usage
Date: Wed, 22 Nov 2006 10:00:13 -0600
To: Log4J Users List <log4j-user@logging.apache.org>

On Nov 22, 2006, at 3:24 AM, Stefano Nichele wrote:

> Hi All,
> I don't know if this is the right list, maybe not and I apologize  
> if this is not the right one. BTW, I would like to know how DEBUG  
> and TRACE level are usually handled.
> I mean, when a log record should be DEBUG and when that should be  
> TRACE ?
> I'm working on a web application and the idea could be: all records  
> useful for an administrator should be DEBUG and not TRACE. At TRACE  
> level just the information useful to the developers could be  
> logged. So, for instance, a value of an "internal" variable should  
> be logged as TRACE. I know this is not easily distinguishable and  
> so I'm wondering how these level are handled from other users.
>
> Thanks
> Ste
>

I suggest using logger names to distinguish messages targeted to  
different audiences.  For example, use logger names based on class  
names for diagnostic messages targeted for developers and some other  
naming system for messages targeted to administrators.  Search the  
archives for "audience" or "audit" and you can find previous  
discussions on this topic.


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