Log customization
Table of contents
Overview
Team Edition uses logback.xml
to configure server logging. This file controls log level and log message pattern.
For details on viewing logs directly in the Team Edition, see Log Viewer.
Default logging configuration
Team Edition's default logback.xml
:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
<layout class="ch.qos.logback.classic.PatternLayout">
<Pattern>
%d{dd-MM-yyyy HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n
</Pattern>
</layout>
</appender>
<statusListener class="ch.qos.logback.core.status.NopStatusListener" />
<logger name="org.jkiss" level="DEBUG" />
<logger name="com.dbeaver" level="DEBUG" />
<logger name="io.cloudbeaver" level="DEBUG" />
<logger name="org.apache.kafka" level="WARN" />
<root level="INFO">
<appender-ref ref="CONSOLE" />
</root>
</configuration>
Customize logging level and pattern
Customize Team Edition logging by creating a custom logback.xml
file:
- Create and save your custom
logback.xml
file on your server. - Mount your custom directory to the container's
/opt/cloudbeaver/cbte/conf/custom
folder. - Restart Team Edition to apply your new logging configuration.
For mounting details, see Docker volumes documentation.
Logging level
Set the logging level in the <root>
element's level
attribute:
ERROR
: logs errors only.WARN
: logs warnings and errors.INFO
: standard logs (recommended for everyday use).DEBUG
: detailed debugging info.TRACE
: maximum verbosity for troubleshooting.
Example:
<root level="WARN">
<appender-ref ref="CONSOLE" />
</root>
To enable detailed logging of GraphQL queries, turn it on in Global preferences.
Logging pattern
Define custom log message pattern in the <Pattern>
element.
Example (time only):
<Pattern>
%d{HH:mm:ss} [%t] %-5level - %msg%n
</Pattern>
Enable detailed logs
To enable detailed logging:
- As administrator, go to Settings -> Administration -> Global preferences.
- Go to Server configuration > Logger.
- Turn on Enable detailed logging.
- Save your changes.
Detailed logs include:
- Session ID and User ID.
- User creation, modification, and logout.
- Resource Manager activity.
- S3/cloud storage actions.
- All GraphQL and administration API parameters.
Passwords, private keys, credentials, and tokens are never logged.