/
Change Log Level on Runtime

Change Log Level on Runtime

Make sure actuator/loggers is only accessible for authorized user or programs, wrong settings can harm your tia Core® product. see Separate Ports for Management to configure a different port for the actuator endpoint to protect it with e.g. your firewall.

Log level can only be changed for tia Core® products that run in a container. The log levels like debug or trace can produce a huge amount of logs and will have an impact to the system performance up to a failure of the system.

 

Configure environment variables:

management.endpoints.web.exposure.include=loggers management.endpoint.loggers.enabled=true


Use a tool like curl or Postman to change the log level:

curl https://<serverDomain>/actuator/loggers/ROOT {"effectiveLevel":"<level>"}

Available Log Level:

Log Level

Description

Log Level

Description

TRACE

only for DEV/TEST systems huge performance impact, very verbose log entries

DEBUG

only for DEV/TEST, in production for exceptional situations, huge performance impact, verbose log entries

INFO

default log level, includes many information, recommended for DEV/TEST system

WARN

only warning and error are logged, very few log entries

ERROR

only errors are in the log. Recommended for production

Related content

Register ArchiveLink exit to call tia Viewer Core function module
Register ArchiveLink exit to call tia Viewer Core function module
Read with this
Example: Logging configuration for JSON logging
Example: Logging configuration for JSON logging
More like this
Update H2 Database from 1.4.199 to 2.2.220
Update H2 Database from 1.4.199 to 2.2.220
Read with this
Configuration of logging framework in container deployment
Configuration of logging framework in container deployment
More like this
tia® Content Server (core)
tia® Content Server (core)
Read with this
Configuration of logging framework in WAR file deployments.
Configuration of logging framework in WAR file deployments.
More like this