Increasing APM logging level selectively for specific logger modules instead of all loggers avoids various problems.

Document ID : KB000047700
Last Modified Date : 14/02/2018
Show Technical Document Details

 Issue: Enabling all log4j loggers instead of selectively choosing the specific logger module can cause performance and logging issues .

 

 Environment:  All APM releases running CLW and other APM components.

 

 Cause: Failing to do this may cause unnecessary DEBUG log messages flooding the EM log besides those specific for CLW. 

 

  Workaround:

   Most APM loggings are implemented with log4j or log4net frameworks.  Their logging levels, e.g. INFO, VERBOSE, DEBUG, TRACE, etc, can be configured for individual logger modules instead of all loggers.  For instance, logging for EM can be set at INFO level:

   log4j.logger.Manager=INFO

 

  while only enabling DEBUG logging on CLW for troubleshooting:

 

  log4j.logger.Manager.CLW=DEBUG

 

 Additional Information:

  https://communities.ca.com/community/ca-apm/blog/2015/06/20/logging-in-ca-apm -- Logging in CA APM 

  http://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.TEC1222321.html - Performance overhead when DEBUG is enabled on EM.