New Webinar: Govern roles, shares, and data movement in Snowflake

Learn how to govern Snowflake roles, shares, and data movement without slowing delivery. Join our live webinar on controlling drift, permissions, and audit readiness.

Save your spot

log-channels

Last updated: September 2, 2025

The log-channels parameter controls which "channels" are logged when running Liquibase commands.

Uses

The channel is shown in each log entry in the second set of brackets. For example, in [2022-05-20 12:52:34] FINE [liquibase.database] Connection has been created the channel is liquibase.database.

Channels are hierarchical, so the above message will be shown if log-channels is set to liquibase or liquibase.database

The default value is liquibase. Multiple channels can be specified by comma-separating them. For example, --log-channels=liquibase,com.microsoft. To enable all logging, regardless of the channel, use --log-channels=all

The level the specified channels are logged at is controlled by the log-level setting, even if that level is OFF.

Syntax

You can set this parameter in the following ways:

Option

Syntax

Liquibase properties file (defaults file)

liquibase.logChannels: <string>

Global flow file argument

globalArgs: { log-channels: "<string>" }

Global CLI parameter

liquibase --log-channels=<string> update --changelog-file=example-changelog.xml

JVM system property (JAVA_OPTS environment variable)

Unix:

JAVA_OPTS=-Dliquibase.logChannels=<string>

Windows:

JAVA_OPTS=-D"liquibase.logChannels"=<string>

Liquibase environment variable

LIQUIBASE_LOG_CHANNELS=<string>