tia Core uses Log4J2 Framework for logging. So the general documentation of this framework applies.
External link to the Apache Log4J project web page: https://logging.apache.org/log4j/2.x/
It is best practice for modifications to Log4J2 configuration to copy existing log4j2-spring.xml file to a custom version (e.g. my.log4j2.xml) that then is modified and linked in by setting logging.conf parameter.
The required logging parameters are:
Parameter | Description | Supported Values | Required | Default value |
| Definition of the log level for the package |
| no | |
| Specifies a location for the configuration file of the logging framework | A path specified absolute or relative to the working directory of tomcat service, e.g. | no |
|
For more information how to apply these parameters, please read Application wide settings .
Log rotation
In production systems, log files can grow large over time and consume disc space as well. Also handling of large log files for issue analysis is getting more difficult. Log rotation refers to an automatic set up to periodically or on trigger event (like log file exceeds a specified size) copy log files aside and keep only a certain number of copies.
Log rotation can be configured by Log4J2 appender.
By default, tia Core implements log rotation using Log4Js RollingFileAppender (see file <webapp>\WEB-INF\classes\log4j2.xml) like this:
tia Core writes the log file
core-of-tia.login the logs sub directory of the web application base directory.At 0:00am and in case the log file exceeds 1GB, it is gz-compressed and renamed to
core-of-tia-<n>.log.gz.Up to 10 compressed log files will be kept before removal.
Note: Utilities like logrotate for Linux (external link: https://linux.die.net/man/8/logrotate) provide similiar functionality on operating system level.
logrotate utility is not shipped with the tia Core cloud image and therefore not available for cloud deployment.