This is an archived version of the documentation for SonarQube-7.2.
See the Latest Documentation for current functionality.

Server Log Management

Server-side logging is controlled by properties set in $SONARQUBE_HOME/conf/

4 logs files are created : one per SonarQube process.

Log Level

The server-side log level can be customized via the sonar.log.level property. Supported values are:

  • INFO (default)

  • DEBUG - for advanced logs.

  • TRACE - show advanced logs and all SQL and Elasticsearch requests. TRACE level logging slows down the server environment, and should be used only for tracking web request performance problems.

Log Level by Process

The server-side log level can be adjusted more precisely for the 4 processes of SonarQube Server via the following property:

  • for the Main process of SonarQube (aka WrapperSimpleApp, the bootstrapper process starting the 3 others)

  • sonar.log.level.web: for the WebServer

  • sonar.log.level.ce: for the ComputeEngineServer

  • for the SearchServer

Log Rotation

To control log rolling, use the sonar.log.rollingPolicy

  • time:[value] - for time-based rotation. For example, use time:yyyy-MM-dd for daily rotation, and time:yyyy-MM for monthly rotation.

  • size:[value] - for size-based rotation. For example, size:10MB.

  • none - for no rotation. Typically this would be used when logs are handled by an external system like logrotate.

sonar.log.maxFiles is the maximum number of files to keep. This property is ignored if sonar.log.rollingPolicy=none.