Hi All! I am trying to find out if I have found a bug, or else have just misunderstood something. I...

# kotlin-logging

[Alec Muffett]

Hi All! I am trying to find out if I have found a bug, or else have just misunderstood something.

I'm learning Kotlin and kotlin-logging; I have some code which looks like:

import ...
private val logger: KLogger = KotlinLogging.logger {}
internal class Engine(private val di: DI) {
    fun mainMethod(args: Array<String>) { // called from "real" main()
        System.setProperty(SimpleLogger.DEFAULT_LOG_LEVEL_KEY, "DEBUG")
        logger.trace("trace")
        logger.debug("debug")
        <http://logger.info|logger.info>("info")
        logger.warn("warning")
        logger.error("error")

...and when it runs, it is (sensibly) printing:

[main] DEBUG psm.Engine - debug
[main] INFO psm.Engine - info
[main] WARN psm.Engine - warning
[main] ERROR psm.Engine - error

HOWEVER: as soon as I declare another logger: KLogger = KotlinLogging.logger {} in another classfile in the same package, the behaviour *changes*; more in comments:

[Alec Muffett]

When there are 2+ logger instances defined, the app snaps back to just printing

[main] INFO psm.Engine - info
[main] WARN psm.Engine - warning
[main] ERROR psm.Engine - error

[Alec Muffett]

So I am wondering whether the second instance is stomping on the DEFAULT_LOG_LEVEL_KEY property? And if so, what's the proper way to set that value at runtime, please?

[Alec Muffett]

Method of setting log level is described on this page as linked-to from this page

[oshai]

did you try setting the properties on startup

[Alec Muffett]

Hi @oshai ! I did not, because that's not what I want to do. I want it dynamically controllable from the app, rather than being a JVM setting.

[Alec Muffett]

This could include, for instance, switching DEBUG logging on and off via a REST API

[oshai]

I am not sure it's possible with simple logger. try log4j or logback