Poor Logging Practice: Multiple Loggers

From OWASP
Jump to: navigation, search


This page was marked to be reviewed for deletion.


#REDIRECT Poor Logging Practice


Last revision (mm/dd/yy): 05/27/2009

Description

It is a poor logging practice to use multiple loggers rather than logging levels in a single class.

Good logging practice dictates the use of a single logger that supports different logging levels for each class.


Risk Factors

TBD

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);
	  ...
	}


Related Attacks


Related Vulnerabilities

Related Controls


Related Technical Impacts


References

Note: A reference to related CWE or CAPEC article should be added when exists. Eg: