Configuring and collecting Verbose logs for the CCS Application Server and/or manager from the CCS console
search cancel

Configuring and collecting Verbose logs for the CCS Application Server and/or manager from the CCS console

book

Article ID: 239617

calendar_today

Updated On:

Products

Control Compliance Suite Control Compliance Suite Standards Server

Issue/Introduction

Control Compliance Suite (CCS)

In the CCS console you can set verbose logging for your Application Server and remote managers in the CCS console, and then have the Console zip up and remotely collect the files from the different CCS components and save them to a user-defined location.

NOTE: See 'Additional Information' below for the KB on how to manually set verbose logging on the different CCS components, and where the log files can be found.

Environment

CCS v12.6.X Consoles

CCS v12.7.X Consoles

Resolution

To set the Log Severity to Verbose on the Application Server

  1. In the CCS Console, navigate to Settings > Deployment View or Grid View.
  2. Right-click on the Application Server and select Configure Log Severity.
  3. From Log Severity, you can select one of the following values:
    1. Warning (This is the default setting) - select Warning to indicate that a potential problem has occurred that may cause serious consequences later if not fixed.
    2. Information - select Information to indicate the normal flow of execution and identify milestone events.
    3. Verbose - select Verbose to indicate the availability of detailed troubleshooting information about events  (Select this option for Verbose Logging)
  4. Click Save. A confirmation message appears that displays the name of the CCS component and the log severity applied. The configured values are set in the service configuration file of the selected CCS component.

 

NOTE: If your Application server also has a Manager installed, also do the followings step:

  1. Find the CCS Manager icon that has the same server name as the Application Server (this represents the manager that is running on the Application Server).
  2. Right-click on the CCS Manager icon and select Configure Log Severity.
  3. From Log Level dropdown, you can select one of the following values:
    1. Not applicable (This is the default for agentless data collection only) – (Select 'Not applicable' if the manager is doing Agentless data collection)
    2. 0 - Error (This is the default setting for agent-based collection) – select 0 - Error to indicate events that cannot be completed because of an error condition.
    3. 1 - Warning – select 1 - Warning to indicate the events that may lead to errors if remediation is not taken.
    4. 2 - Notice – select 2 - Notice to indicate the events that need attention but no error condition.
    5. 3 - Information – select 3 - Information to indicate a successful event.
    6. 4 - Data –  select 4 - Data to indicate that it can be used by developers to tag a relevant log statement of an in-memory data structure or a class object member values for more verbose information.
    7. 5 - Debug – select 5 - Debug to indicate the events that include granular information for troubleshooting.
    8. 6 - Trace – select 6 - Trace to indicate the events that include step-by-step progress information of an event, which may be useful for audit and review.   (Select 'Trace' if the manager is doing agent-based data collection)
  4. Click Save

 

To set Log Severity to Verbose and Log Level on a Remote CCS Manager

  1. In the CCS Console, navigate to Settings > Deployment View or Grid View.
  2. Right-click a CCS Manager and select Configure Log Severity.
  3. From Log Severity, you can select one of the following values:
    1. Warning (This is the default setting) - select Warning to indicate that a potential problem has occurred that may cause serious consequences later if not fixed.
    2. Information - select Information to indicate the normal flow of execution and identify milestone events.
    3. Verbose - select Verbose to indicate the availability of detailed troubleshooting information about events    (Select this option for Verbose logging)
  4. From the Log Level dropdown, you can select one of the following values:
    1. Not applicable (This is the default for agentless data collection only) – (Select 'Not applicable' if the manager is doing Agentless data collection)
    2. 0 - Error (This is the default setting for agent-based collection) – select 0 - Error to indicate events that cannot be completed because of an error condition.
    3. 1 - Warning – select 1 - Warning to indicate the events that may lead to errors if remediation is not taken.
    4. 2 - Notice – select 2 - Notice to indicate the events that need attention but no error condition.
    5. 3 - Information – select 3 - Information to indicate a successful event.
    6. 4 - Data –  select 4 - Data to indicate that it can be used by developers to tag a relevant log statement of an in-memory data structure or a class object member values for more verbose information.
    7. 5 - Debug – select 5 - Debug to indicate the events that include granular information for troubleshooting.
    8. 6 - Trace – select 6 - Trace to indicate the events that include step-by-step progress information of an event, which may be useful for audit and review.   (Select 'Trace' if the manager is doing agent-based data collection)
  5. Click Save. 
    A confirmation message appears that displays the name of the CCS Manager and the log severity and log level applied. The configured values are set in the C:\Program Files (x86)\Symantec\CCS\Reporting and Analytics\DPS\AgentManagerlogger.conf configuration file of the selected CCS Manager.

 

Duplicate the issue and then collect logs from the Application Server or remote Manager

   by doing the following:

  1. After you have set the logging to verbose on your Application Server and/or Managers, duplicate the issue you are troubleshooting.  Once you have duplicated the issue, collect the logs from the different CCS components.
  2. On the CCS Console, navigate to Settings > Deployment View or Grid View.
  3. Right-click a CCS component(s) that you enabled verbose logging and select Collect CCS Logs.
  4. Browse and select a directory location on the CCS Console system to save the compressed log files collected from the selected CCS component.
    NOTE: A confirmation message appears that displays the name of the zipped folder that contains the compressed log files and the user-defined directory location in which the compressed log files are downloaded and saved. The compressed logs include logs related to the selected CCS component only.
  5. Attach the saved zip file(s) to the Broadcom support case to be reviewed by CCS Technical Support.

 

How to set the logging on the Application Server and/or CCS Managers back to default after the issue has been duplicated

Once you have duplicated the issue and attached the verbose logs to the case, make sure you set the Logging level on your CCS components back to the default setting to decrease the load that verbose logging creates when enabled. 

  1. In the CCS Console, navigate to Settings > Deployment View or Grid View.
  2. Right-click on the CCS Component you would like to set back to default logging and select Configure Log Severity.
  3. Depending if you are using Agentless or Agent-Based collection, do the following:
    1. Agentless collection:
      Log Severity to Warning
      Log Level       to Not Applicable
    2. Agent-based collection:
      Log Severity to Warning
      Log Level to 0 - Errors
  4. Click Save.

 

How to determine what Log Level is currently set on the Application Server and/or CCS Managers

Follow the steps below to determine what Logging Level is currently enabled on your Application Server and/or CCS Managers:

Refresh the log level of the CCS Components in the Console to make sure the logging level is updated

  1. In the CCS Console, navigate to Settings > Deployment View or Grid View.
  2. In the Infrastructure Tasks dropdown, select Monitor System Jobs.  This will allow you to see the jobs that are currently running.
  3. Also in the Infrastructure Task dropdown, select Sync Configuration, and when that is finished select Refresh Health Status.

To check the log level of the Application Server:

  1. Once both the Sync Configuration and Refresh Health Status have finished, right-click on the CCS component you would like to see what the logging level is set at and select Health & Status Details.
  2. On the Application server, in the left-hand column select Logging Details under the 'Application Server on <App_server_hostname>' header.  Once that is selected, expand the Application Server Log settings in the right panel.  The Overall Severity will show what severity the Application Server is currently set at (ignore any other settings listed as verbose as that is normal).  Overall Severity set to Warning is the default setting.  If Overall Severity is set to Verbose then verbose logging is enabled, etc.
    NOTE: If your Application Server also has a Manager installed, see the section below on how to determine the logging level on a CCS manager that is installed on the Application Server

To check the log level of a remote CCS Manager

  1. Once the Sync Configuration and Refresh Health Status have finished, right-click on the CCS manager you would like to see what the logging level is set at and select Health & Status Details.
  2. In the left-hand column select Logging Details under the 'CCS Manager Service on <hostname>' header.  Once that is selected, expand the CCS Manager Service Log Settings in the right panel.  The Overall Severity will show what severity the CCS Manager is currently set at (ignore any other settings listed as verbose as that is normal).  Overall Severity set to Warning is the default setting.  If the Overall Severity is set to Verbose then verbose logging is enabled, etc.

 

Additional Information

How to manually set verbose logging on the CCS Application server and/or Remote managers:

https://knowledge.broadcom.com/external/article?articleId=163985

Powered by Wolken Software