Configuring the log level on the Controller

OpenText ScanCentral SAST logs typically provide enough information to follow the flow of operations under normal conditions. If things are not working as expected, the logging might not provide enough information to determine the actual root cause of the issue. If the Controller log information is insufficient, you can increase the amount of information by changing the log level. The following instructions describe how to configure the log level on the Controller. For instructions on how to change the log level on sensors and clients, see Enabling debugging on clients and sensors.

To configure the log level on the Controller:

Open the <controller_install_dir>/tomcat/webapps/scancentral-ctrl/WEB-INF/classes/log4j2.xml file in a text editor.

Locate one of the following strings:

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

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

For a more detailed level of logging, change the level as shown in the following example:
```
<Logger name="com.fortify.cloud" level="debug" additivity="false">
```

To apply the change, restart the Controller.

For more information about log levels and defining custom log levels, see the Apache Logging Services website

Configuring the Controller logging

Locating log files