This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Poor Logging Practice: Multiple Loggers"
From OWASP
Weilin Zhong (talk | contribs) (→Abstract) |
Weilin Zhong (talk | contribs) (→Description) |
||
| Line 8: | Line 8: | ||
==Description== | ==Description== | ||
| − | Good logging practice dictates the use of a single logger | + | Good logging practice dictates the use of a single logger that supports different logging levels for each class. |
==Examples == | ==Examples == | ||
Revision as of 16:00, 21 July 2006
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
- This article includes content generously donated to OWASP by
Abstract
It is a poor logging practice to use multiple loggers rather than logging levels in a single class.
Description
Good logging practice dictates the use of a single logger that supports different logging levels for each class.
Examples
The following code errantly declares multiple loggers.
public class MyClass {
private final static Logger good =
Logger.getLogger(MyClass.class);
private final static Logger bad =
Logger.getLogger(MyClass.class);
private final static Logger ugly =
Logger.getLogger(MyClass.class);
...
}
