Configuring the Logging Level on the Controller

ScanCentral SAST logging typically provides enough information to follow the flow of operations under normal conditions. If things are not working as expected, the logging may not provide enough information to determine the actual root cause of the issue.

In the event that ScanCentral SAST does not provide enough information to diagnose a situation, you can increase the amount of information that is logged. The following steps describe how to configure the logging level on the Controller. For instructions on how to change the logging level on sensors, see "Configuring the Logging Level for Sensors " on page 1.

To configure the logging level on the Controller:

  1. Navigate to <controller_dir>/tomcat/webapps/scancentral-ctrl/WEB-INF/classes, and open the log4j2.xml file in a text editor.

  2. Locate one of the following strings:

    • <Logger name="com.fortify.cloudscan" level="info" additivity="false">

    • <Logger name="com.fortify.cloudscan.ctrl.service" level="info" additivity="false">

  3. For a more detailed level of logging, change the level, as follows:

    <Logger name="com.fortify.cloudscan" level="debug" additivity="false">

    Standard log levels supported by log4j2.xml are as follows.

    Standard Level intLevel
    OFF 0
    FATAL 100
    ERROR 200
    WARN 300
    INFO 400
    DEBUG 500
    TRACE 600
    ALL Integer.MAX_VALUE

  4. To apply the change, restart the Controller.

For more information about defining custom log levels, see the Apache Logging Services website (https://logging.apache.org/log4j/2.x/manual/customloglevels.html).

See Also

Enabling Debugging on Clients and Sensors