How to increase the log level for CMDB Visualizer (17.2 RU9 and above, 17.3 RU1 and above)

Products

• CA Service Management - Service Desk Manager
• CA Service Desk Manager

Issue/Introduction

Starting from 17.2 RU9 and 17.3 RU1, CMDB Visualizer has been updated with modern technology to replace Adobe Flash Player.

Here the steps to increase the log level.

Environment

CA CMDB Visualizer

• 17.2 RU9 and above
• 17.3 RU1 and above
• 17.4 and above

Resolution

1. Increase the log level for visualizer_slump.log  and visualizer_bop.log under NX_ROOT\bopcfg\www\CATALINA_BASE_VIZ\logs

1.1 Edit NX_ROOT\bopcfg\www\CATALINA_BASE_VIZ\webapps\CMDBVisualizer\WEB-INF\classes\log4j.properties or log4j2.properties

1.2 Change from INFO to debug log4j.rootCategory and log4j.logger.bop_logging

Example:

log4j.rootCategory=debug, jcasmodata

log4j.logger.bop_logging=debug jcasmbop

You can also increase the log level for the slump package and bop package by changing to debug log4j.logger.com.ca.ServicePlus.slump and log4j.logger.com.ca.sdm.bop. 

Example:

log4j.logger.com.ca.ServicePlus.slump=debug

log4j.logger.com.ca.sdm.bop=debug

2. Increase the log level for VisualizerMS_debug.log under NX_ROOT\log

2.1 Edit NX_ROOT\bopcfg\www\CATALINA_BASE_VIZ\webapps\CMDBVisualizer\WEB-INF\classes\logback.xml

2.2 Comment out:

  <root level="INFO">
    <appender-ref ref="ASYNCFILE" />
  </root>

2.3 Uncomment 

  <root level="DEBUG">
    <appender-ref ref="DEBUGFILE" />
  </root>

Example:

 <!-- 
  <root level="INFO">
    <appender-ref ref="ASYNCFILE" />
  </root>
  -->
 
  <root level="DEBUG">
    <appender-ref ref="DEBUGFILE" />
  </root>

2.4 Save Changes

Additional Information

Troubleshooting CMDB Visualizer

CMDB Visualizer Resource Management and Performance Tuning