Viewing ScanCentral Logs

To retrieve the ScanCentral Controller log, navigate to <controller_dir>\tomcat\logs\scancentralCtrl.log.

To view the ScanCentral client and sensor logs on a Windows system:

• Navigate to %FORTIFY_HOME%\scancentral-<version>\log, where %FORTIFY_HOME% is %LOCALAPPDATA%\Fortify.

  On Windows 10, for example, the location is

  C:\Users\<user>\AppData\Local\Fortify\scancentral-<version>\log

• To retrieve the ScanCentral SAST log on a Linux system, navigate to
  ~/.fortify/scancentral-<version>/log/scancentral.log.

Enabling Debugging on Clients and Sensors

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.

If ScanCentral SAST does not provide enough information to diagnose a situation, you can configure the logging level for the clients and for sensors. To increase the log level for clients and sensors, use the use the -debug command-line option. (See Global Options.) Make sure that you specify the -debug option before the action (start, retrieve, and so on).

Examples:

The next time the sensor is called, the log contains debug-level information.

For information about how to configure the logging level for the Controller, see Configuring the Logging Level on the Controller.