Configure Composer Logs
The microservices used in Composer write logs to their corresponding service's log files by default. You can configure Composer to write these logs to the console only, or to write logs both to the console and the service's log files.
Every service config file includes two properties you can use to define where the logs are written:
log.console.level- edit to define the types of logs to write to the console
log.file.level- edit to define the types of logs to write to the files
If you install using the bootstrap script, logging to files is enabled by default. You can reroute the logging to the console as needed to customize your installation.
Bootstrap installation: The
log.file.level=ALLto support compatibility with earlier versions of Composer.
The following table lists possible values for
|All available log information.|
|Application error messages that may affect processes.|
|Unexpected application issues that may not affect processes.|
|Triggers capture of |
Enable logging to the console and append the desired corresponding value of the properties to the appropriate service configuration file.
log.console.level=ALLto route duplicates of all logs to the console.
log.console.level=ERRORto route only duplicates of errors to the console.
log.console.level=ERRORto have all logs in files and errors duplicated to the console.
Adjust the values to meet your needs, then restart the service after you've edited the config.
Composer services have two config files,
*.jvm. If you add log configuration properties to both files, the priority of
*.jvm is higher than
By default, Consul writes logs to the console, but you can duplicate logs to files if needed.
Configure Consul Logs to Duplicate to Files:
Edit the Consul config file,
consul.json. For Linux installations, this is located in
Add the following properties:
"log_rotate_max_files" : 5
Adjust the path to your log file and other log configuration properties as needed for your environment. In Linux environments, the log is located in
/opt/zoomdata/logs, and in
<install-path>/logsfor Windows environments. See Consul documentation for more information.