KonzeptLogging is the tracking of application events of a system into one or more log files in parallel to its processing. Events for logging may refer to receiving a request from external sender, starting or ending the processing a task, the system raising error or exception, or other, so that in case of an issue with the system, the processing can be reconstructed and analyzed.
The logging behavior can be configured in order to produce more (i.e. when reproducing an issue) or less (in a well-running production system) log information. Besides the log row format, there is the configuration of the log level (i.e. only tracking error-events respectively tracking error-, warning-, information- and debug messages), as well as the configuration of which system component should be traced.
Also configurable is how log files are organized (i.e. start every day a fresh log file) and how long they are getting kept (i.e. remove after 7 days, or when a limit for disc space allocation by log files is exceeded). This configuration is typically referred to as “log rotation”.
There are multiple options to deploy tia Core and configuration varies depending on the selected way of deployment:
As web application context to a Tomcat web application server ( .war-file deployment )
As Spring-Boot fat java archive (fat jar deployment)
As Spring Boot native binary (
Spring native deployment)[AF1]-logstash
Using tia Core container image for cloud deployment[AF2]
...
[AF1]Future Spring 3 Native binary (as planned to be used ~Nov 2023) will no more support log4J2, so other logging approach is required.
==> can't be documented now
[AF2]Logging approach for container/cloud deployment is writing logs to stdout only. At this point it depends on customer's cloud architecture to pick it up.