Versions Compared

Version Old Version 14 New Version 15
Changes made by

Simone Conrad

Armin Franke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Hint: Logs written to stdout or stderr may also be viewed by docker command (if using another container runtime, please refer to its documentation):

  • Code Block
    docker container logs <container name or id>

Using this command with option -f allows to watch log file tail continuously.

...

Info

Recommended in cloud-environments is also the logging in JSON format available since tia® Core Content server 3.4.0. To configure JSON logging, set login.config parameter to value /application/config/json-logback.xml .

Using war-deployment, log rotation is activated by default:

...

Parameter

Description

Supported Values

Required

Default value

logging.level.root

Log Level for all logging.

If log level for package is configured, package configuration will overrule.

Recommended for Production is WARN or ERROR.

OFF

ERROR

WARN

INFO

DEBUG

no

DEBUG

logging.level.<package>

Example:

logging.level.com.software.kgs

Definition of the log level for the package.

 

OFF

ERROR

WARN

INFO

DEBUG

no

 

logging.config

Specifies a location for the configuration file of the logging framework.

Info

Hint: When using container-deployment volume mapping maybe required.

Path and filename

no

log4j2.xml

...

Info

Note: Utilities like logrotate for Linux (external link: https://linux.die.net/man/8/logrotate) also provide comparable functionality at operating system level.

logrotate utility is not shipped with the tia Core cloud image and therefore not available forcloud deployment.

...