Logging Configuration
- Last Updated: May 13, 2026
- 1 minute read
- Semaphore
- Documentation
Within KMM (and the other services provided as part of the Semaphore Studio application) we use quarkus as the web container and take advantage of its logging capabilities.
If the default logging set up is not correct for your needs, you can change override the default settings by providing them as arguments to the start up script (the relevant start.sh file for linux, or the relevant .cmd file for windows). You can add quarkus logging settings in the same style as the
quarkus.http.host
setting that is already present.
The properties available are documented at https://quarkus.io/guides/logging, but as an example, you can set
-Dquarkus.log.file.rotation.max-file-size=1M
-Dquarkus.log.file.rotation.max-backup-index=2
-Dquarkus.log.level=WARN
To reduce the size of each log file, to only keep the current log file and the previous 2 and to log at the WARN level.
Note, we do not recommend that you change the log level - when something goes wrong, the log file is an important resource in detecting what happened.
Each Publish even creates a new log file - this behaviour cannot be changed.