General Usage Best Practices › Rerun Failed Tasks with Debug Logging

Rerun Failed Tasks with Debug Logging

When a CA CSM task fails, we recommend that you turn on debug logging and redo the steps that led to the error.

Follow these steps:

1. Navigate to the Settings page and click the Change Diagnostic Log Level link in the Action area in the left pane.

   The Change Diagnostic Log Level dialog appears.

2. Set the following values, and click OK:

   Log Level

   Set to DEBUG.

   Reset the Log Level After the First Task Is Started

   Ensure that this check box is selected (default).

   Include Logs in the Task Output

   Select this check box.

   Task Logging Directory

   Specify the USS directory where log information is stored. The directory should have sufficient space for saving log files. Otherwise, no log information is displayed for new tasks in the task output browser.

3. Redo the steps that led to the problem.

   The details of the tasks you performed are saved to the task output browser. A dialog that shows the progress of the task opens. When the task completes, you can click Show Results on the Progress tab to close this dialog. The task output browser opens and you can view the action details. Click Close to close the task output browser.

   Note: While a task is in progress, you can perform other work. You can click Hide to exit the dialog and view the task status later on the Tasks tab.

4. Go to the Task tab, locate the new task with a Diagnostic Log entry, and export it to ZIP.

   The ZIP file is saved to your computer.

5. Open an issue on the CA Support Online website and attach the ZIP file to this issue.

   Note: You can review this file in preparation for your communication with CA Support.

Business Value:

Using this best practice can help save you time collecting the appropriate information when you encounter problems with CA CSM and are working with CA Support.

Additional Considerations:

After contacting support and resolving the issue, do the following:

• Consider deleting the task because it can take up valuable space in your CA Datacom/MSM database and USS directories.
• Purge logs files regularly because, depending on your settings, logs are written whenever a task is run by any user, so they can accumulate quickly.
• Change the Log Level setting back to NONE. Only turn on debug logging when you are experiencing problems.

More Information:

For more information, see the online help.