On 27/02/07, Rafael H. Schloming (JIRA) <[email protected]> wrote:
define standard logging levels to be used -----------------------------------------Key: QPID-392 URL: https://issues.apache.org/jira/browse/QPID-392 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client, Java Broker, Java Client, Java Clustering, Java Common Reporter: Rafael H. Schloming Currently logging is very verbose and difficult to read. We need to explicitly define and use of standard logging levels. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
In the Java code base we use log4j however there seems to be disagreement in who the levels are targeted at. I would argue that all logging is for developers info,debug and trace should be on a per class basis. The level to use should be based on the amount of logging it will generate. If the message is very rare and high level then info if it happens a lot it should be trace. warn and error should be used to highlight unusual conditions. I'm sure that in production most systems will be run with from the info,warn or error level. For debugging we should be using the xml configuration to limit the logging to the classes we are interested in. -- Martin Ritchie
