Configuring and Using Diagnostic Tools › Manage the Debug Level for Specific Modules

Manage the Debug Level for Specific Modules

As an administrator, you can use the Debug Controller page to activate, adjust, and manage the debug features of individual CA SOI server modules. You can perform the following tasks on this page:

• Enable (ON) or disable (OFF) the debug state of the module.
• Specify the appropriate granularity (OFF, MIN, MOD, and MAX) for the debug level.
• Specify whether to repeat the debug output of any selected module into a separate log file specific to that module. The separate (Sep) option on the page provides this functionality. You can also specify whether to repeat the debug output of all selected modules into the same file. The group (Grp) option provides this functionality. You can specify these settings by using the advanced options. Also, consider the following points when using the separate and group options:
  • Separate (Sep) and group (Grp) options are not mutually exclusive.
  • You can activate any number of separate and group options simultaneously.
  • The Repeater log output is emitted only if debug for the module is turned on.
  • If the debug level of the module is turned off, the repeater log output is also turned off.

Note: The debug Console is designed to be used only with help from CA Technical Support.

Follow these steps:

1. Click Start, Programs, CA, Service Operations Insight, CA Service Operations Insight User Interface.
2. Enter the appropriate user credentials.

   The Administration UI opens.

3. Click the Administration tab.

   The administration options appear in the left pane.

4. Click the plus sign (+) next to the CA Service Operations Insight Manager Configuration option.

   The available servers appear.

5. Click the name of the required server.

   The page that opens contains the Debugging And Logs button.

6. Click Debugging And Logs and then click the Debug Controller link.

   The Debug Controller page opens.

7. Set the debug level for the specific module as follows:

   Note: You can use the Info icon tooltip (Info column) to view detailed information about the function that a specific module performs.

   • Select ON or OFF in the Desired State column to set the debug state for the module.
   • Select OFF, MIN, MOD, or MAX in the Desired Level column to set the desired debug level granularity.
   • Click the Apply button to save the settings.

     The Current State and Current Debug Level columns start showing the updated state.

   Note: If the entry in the Module Handle column is truncated, the entry tooltip shows the complete debug handle string (used in the web.xml setup) for the module.

8. Click the Advanced Options button if you want to specify the repeater options: separate (Sep) and group (Grp).

   The Debug Controller page is updated with the Repeater Logs column appearing next to the Module Handle column.

9. Select the appropriate repeater option for the module as follows:

   Sep

   Allows the logging subsystem to repeat the debug output of any selected module into a separate log file that is dedicated to that module. The tooltip of the separate option (Sep) shows the name of the associated log file. This name is derived from the abbreviated name of the module. For example, if the Sep option is checked for the Action Service module, the debug output of the module is duplicated and logged into the dbg-rpt-actionservice.log file.

   Grp

   Allows the logging subsystem to repeat the debug output of all selected modules into the same file. The name of the log file that is associated with the group option (Grp) is fixed as dbg-rpt-customlog.log. For example, if the Grp option is checked for the Action Service and Action Retry Config modules, their debug output is duplicated and combined into the dbg-rpt-customlog.log file.

10. Click Apply.

    The settings are saved.