Enable CA Service Catalog's TRACE (or DEBUG) level for diagnostic purposes
search cancel

Enable CA Service Catalog's TRACE (or DEBUG) level for diagnostic purposes

book

Article ID: 12894

calendar_today

Updated On:

Products

CA Service Catalog

Issue/Introduction

The following instructions describe how to enable debug logging in Catalog, as written to the view.log file (located in C:\Program Files\CA\Service Catalog\logs).  Tracing may be of value to determine on functionality and behaviour of the CA Service Catalog product

Environment

CA Service Catalog, 17.x version.

Resolution

  1. Backup the file log4j.xml, located in under %USM_HOME%\view\conf\, to a separate directory.

  2. Edit the file log4j.xml, located in under %USM_HOME%\view\conf\, with a text editor.

  3. Locate this line (around line 78)
    <Logger name="com.ca" level="info">
  4. Modify this line to read as:
    <Logger name="com.ca" level="DEBUG">
  5. Toward the bottom of the log4j.xml file, locate this line:
    <Root level="warn">

    Modify this line to read as:
    <Root level="DEBUG">

The change takes  effect immediately. There is no need to recycle the CA Service Catalog service. 

 

NOTE:  Please use TRACE if you are looking to obtain performance statistics on SQL commands.

Edit the file log4j.xml, located in under %USM_HOME%\view\conf\, with a text editor.

  1. Locate this line (around line 78)
    <Logger name="com.ca" level="info">

    Modify this line to read as:
    <Logger name="com.ca" level="TRACE">
  2. Toward the bottom of the log4j.xml file, locate this line:
    <Root level="warn">

    Modify this line to read as:
    <Root level="TRACE">

The change takes  effect immediately. There is no need to recycle the CA Service Catalog service. 

 

Additional Information

TRACE mode and DEBUG mode are two different methods to enable extended logging.  TRACE mode is not a subset of DEBUG; setting the logging to DEBUG will not display TRACE messages and vice versa

Reversing the Logging

To undo the tracing, restore the log4j.xml file from the backup per the above instructions.  Save the TRACE level log settings first to another file, in case they are needed in the future.

 
NOTE: Do NOT leave the logging running unless it is required to troubleshoot a specific issue.