Configuration of logging framework in container deployment
- Armin Franke
- sebastian.goretzka
- Stefan Franz
This article focuses on container-deployment of tia® Core products.
By default, tia® Core logs to Standard out.
There it may be read by observability tools.
Hint: Logs written to stdout or stderr may also be viewed by docker command (if using another container runtime, please refer to its documentation):
docker container logs <container name or id>
Using this command with option -f allows to watch log file tail continuously.
Custom configuration
The log level can be configured for the complete product (parameter logging.level.root), or for a special module only (parameter logging.level.<package>).
The log row format, the log location, and other can be configured in a log configuration file (the default file shipped with the product is logback-spring.xml). It is recommended to create a new logging configuration file. Use parameter logging.config to point to the custom configuration file.
The logging framework included in tia® Content Server Core is SLFJ4-compliant. For documentation refer to the https://www.slf4j.org/manual.html. Since tia® Content Server Core Release 3.0.0 this is Logback framework (see Logback Home).
tia® Content Server Core parameters for logging:
Parameter | Description | Supported Values | Required | Default value |
| Log Level for all logging. If log level for package is configured, package configuration will overrule. Recommended for Production is WARN or ERROR. |
| no |
|
Example:
| Definition of the log level for the package.
|
| no |
|
| Specifies a location for the configuration file of the logging framework. | Path and filename | no |
|
For more information how to apply these parameters, please read Application wide settings.
For example logging configuration files see: