# Turning off logging in Liquibase 4.11

**URL:** <https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969>\
**Category:** General Discussion\
**Tags:** 411, logging\
**Created:** [June 14, 2022, 5:32pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969 "2022-06-14T17:32:38Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![ggb667](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/ggb667/32/783_2.png) [@ggb667](https://forum.liquibase.org/u/ggb667)\
**Post date:** [June 14, 2022, 5:32pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/1 "2022-06-14T17:32:38Z")

</div>

I’m trying to get help with logging and my post got blocked!!!

---

<div class="post-metadata">

**Author:** ![ggb667](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/ggb667/32/783_2.png) [@ggb667](https://forum.liquibase.org/u/ggb667)\
**Post date:** [June 14, 2022, 5:34pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/2 "2022-06-14T17:34:58Z")

</div>

I need assistance, how can I ready some of the support staff?

---

<div class="post-metadata">

**Author:** ![tabbyfoo](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/tabbyfoo/32/748_2.png) [@tabbyfoo](https://forum.liquibase.org/u/tabbyfoo)\
**Post date:** [June 14, 2022, 5:58pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/3 "2022-06-14T17:58:28Z")

</div>

Hi there, @ggb667 - Thanks for reaching out! Our Akismet filtering is sometimes a little over-enthusiastic about protecting the forum from spammers, but rest assured, your post was not blocked, it was just put in a queue for us to review and make sure it wasn’t spam. It’s been approved and should be live on the site. If you’re a Liquibase Pro or Enterprise user, you also have access to our customer success team for support, and they can be reached from this page: [Expert Liquibase Support | Liquibase.com](https://www.liquibase.com/support)

Kind Regards,  
Tabby  
Technical Community Manager

---

<div class="post-metadata">

**Author:** ![ggb667](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/ggb667/32/783_2.png) [@ggb667](https://forum.liquibase.org/u/ggb667)\
**Post date:** [June 15, 2022, 2:21pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/4 "2022-06-15T14:21:49Z")

</div>

Thank you. I (and my whole team at John Deere actually) are having extreme problems getting logging working in 4.11.0 liquibase. We are trying to set the logging to OFF when doing testing, or maybe WARN or SEVERE, but none of the dozens of ways we have tried to configure it have worked. The only thing that had ANY effect at all is setting the overall maven logging level, but that affects everything, not just liquibase and we can’t really run that way.

---

<div class="post-metadata">

**Author:** ![ktaggart](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/ktaggart/32/596_2.png) [@ktaggart](https://forum.liquibase.org/u/ktaggart)\
**Post date:** [June 15, 2022, 2:33pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/5 "2022-06-15T14:33:51Z")

</div>

Liquibase now follows the maven log configuration, we no longer have our own special set up for maven logging.

You should be able to set certain channels via maven so it doesn’t set the logging for everything.

I believe this is the PR that implemented the change [Mark liquibase-maven-plugin logging configuration as deprecated by nvoxland · Pull Request #2261 · liquibase/liquibase · GitHub](https://github.com/liquibase/liquibase/pull/2261)

---

<div class="post-metadata">

**Author:** ![ggb667](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/ggb667/32/783_2.png) [@ggb667](https://forum.liquibase.org/u/ggb667)\
**Post date:** [June 15, 2022, 6:48pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/6 "2022-06-15T18:48:39Z")

</div>

Is there a maven pom example that shuts up the logging to a reasonable level?

---

<div class="post-metadata">

**Author:** ![ggb667](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/ggb667/32/783_2.png) [@ggb667](https://forum.liquibase.org/u/ggb667)\
**Post date:** [June 16, 2022, 9:46pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/7 "2022-06-16T21:46:49Z")

</div>

Configuration changes seem to have no effect whatsoever on making it be quiet.

---

<div class="post-metadata">

**Author:** ![ggb667](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/ggb667/32/783_2.png) [@ggb667](https://forum.liquibase.org/u/ggb667)\
**Post date:** [June 22, 2022, 7:09pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/8 "2022-06-22T19:09:53Z")

</div>

I believe logback is also in use.

---

<div class="post-metadata">

**Author:** ![nvoxland](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@nvoxland](https://forum.liquibase.org/u/nvoxland)\
**Post date:** [June 23, 2022, 6:54pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/9 "2022-06-23T18:54:30Z")

</div>

Yes, maven uses slf4j for logging and we hook into that.

So by default it will log everything across all the plugins (including liquibase) with info level logging. The `-X` maven argument will log everything (including liquibase) at fine level.

If you want to control the logging of specific logging channels, you can do that as well [Maven – Maven 3.1.x logging](https://maven.apache.org/maven-logging.html) has a not super detailed pointer, but does list the `${maven.home}/conf/logging/simplelogger.properties` file where it has the maven-install-specific defaults, and how you can add -D flags to MAVEN\_OPTS to override those defaults on a per-call basis.

One of those is `org.slf4j.simpleLogger.log.a.b.c` for the level for the channel. So you could use `org.slf4j.simpleLogger.log.liquibase=warn` to limit the liquibase logging level to “warn”

Nathan

---

<div class="post-metadata">

**Author:** ![ggb667](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/ggb667/32/783_2.png) [@ggb667](https://forum.liquibase.org/u/ggb667)\
**Post date:** [July 1, 2022, 3:35pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/10 "2022-07-01T15:35:28Z")

</div>

I tried

export MAVEN\_OPTS=“-Dorg.slf4j.simpleLogger.log.liquibase=ERROR -Dliquibase.sql.logLevel=ERROR -Dliquibase.logLevel=ERROR”

but it was completely ignored.

Still getting a ton of  
INFO: ChangeSet database/static-data.xml::static-test-data-clear-reference-chemical-table::as77566 ran successfully in 8ms  
Running Changeset: database/static-data.xml::static-test-data-clear-fertilizer-table::as77566  
Jul 01, 2022 3:34:41 PM liquibase.changelog  
INFO: Data deleted from FERTILIZER  
Jul 01, 2022 3:34:41 PM liquibase.changelog

---

<div class="post-metadata">

**Author:** ![ggb667](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.liquibase.org/ggb667/32/783_2.png) [@ggb667](https://forum.liquibase.org/u/ggb667)\
**Post date:** [July 1, 2022, 4:37pm UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/11 "2022-07-01T16:37:38Z")

</div>

I also tried insanity like this:

```auto
            Logger schemaUpdate = (Logger) LoggerFactory.getLogger(SchemaUpdate.class);
            schemaUpdate.setLevel(Level.ERROR);
            OutputStream os = new LogOutputStream(schemaUpdate);
            Writer output = new OutputStreamWriter(os);
            LoggingExecutor loggingExecutor = new LoggingExecutor(Scope.getCurrentScope().getSingleton(ExecutorService.class).getExecutor("jdbc", lbase.getDatabase()), output, lbase.getDatabase());
            Scope.getCurrentScope().getSingleton(ExecutorService.class).setExecutor("logging", lbase.getDatabase(), loggingExecutor);
            Scope.getCurrentScope().getSingleton(ExecutorService.class).setExecutor("jdbc", lbase.getDatabase(), loggingExecutor);

```

---

<div class="post-metadata">

**Author:** ![anon1](https://avatars.discourse-cdn.com/v4/letter/a/e47774/32.png) [@anon1](https://forum.liquibase.org/u/anon1)\
**Post date:** [April 11, 2026, 10:21am UTC](https://forum.liquibase.org/t/turning-off-logging-in-liquibase-4-11/6969/12 "2026-04-11T10:21:56Z")

</div>

The issue is Liquibase using the ConsoleUIService by default. ConsoleUIService prints messages like ‘Running ChangeSet:’ directly to standard out. To have your Logging Level apply you need to set Scope.Attr.ui.name() to a LoggerUIService in the scopeValues for your Scope. For example:

```java
Map<String, Object> scopeValues = new HashMap<>();
scopeValues.put(Scope.Attr.ui.name(), new LoggerUIService());
Scope.child(scopeValues, yourRunner);

```