does kotlint-logging support mocking the logger?

I’m using kotlin-logging, finding that it seems pretty random but sometime you have to add a newline or your next log message ends up stuck to the end of the prior one…

hi guys! is it possible to configure colorful logging in java app based on log level? like it done in android logcat

does kotlin-logging work on ios?

I'm doing some json formatting of our logs using logback config. We use kotlin-logging in our app. Does anybody have an example / doc on how to capture logging output to assert against in a unit test from kotlin-logging?

Hey all. I have a project that has a dependency that has a bunch of log statements using Kotlin logger. When I run my project, I can see the depdency's DEBUG and INFO level logs, but not TRACE level logs (which I need to see). I have tried slf4j

SimpleLogger

with configuration

System.setProperty(org.slf4j.impl.SimpleLogger.DEFAULT_LOG_LEVEL_KEY, "TRACE")

but could still not see trace level logs. I then switched to

slf4j-log4j12

to rule out

SimpleLogger

issues, with config file

log4j.rootLogger=TRACE, STDOUT
log4j.logger.deng=TRACE
log4j.appender.STDOUT=org.apache.log4j.ConsoleAppender
log4j.appender.STDOUT.layout=org.apache.log4j.PatternLayout
log4j.appender.STDOUT.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n

and still no trace logs show. Any ideas what I'm doing wrong?

and thats what confuses me.. is there some sort of seperate debug only configuration that i have not set or so..

in evaluatted scripts i get this output:

14:49:03.787 [main] .(null:7)   INFO  - >>>> executing step two

instead of null i would expect scriptFile.kts

Is there a recommended way to use a logger from a public inline function? I could do

@PublishedApi internal val logger = KotlinLogging.logger {}

but that would get confusing with my other loggers. Should I just give it a unique name or is there a better way?

I’m asking because in my logback conf I specify using debug but I can’t see any debug logs when the application runs. What else do I need to do?

Native or JVM?

so for my multiplatform app (jfx, js and ktor server on jvm) i want to add better logging i guess kotlin-logging seems to be ready to try but i have some questions.. like why are the

msg: () -> Any?

not

inline

, that would make some stuff where i call suspending stuff possible i guess that would break compatibility with the slf4j stuff ?

also can i use kotlin-logging to also read the log messages that have been sent ? i want to add a logger panel to my client if possible

seems like the code on github is.. outdated ? there is 1.7.6 on maven but in the buildscript is https://github.com/MicroUtils/kotlin-logging/blob/master/build.gradle.kts#L15

How does defining kotlin-logging works with libraries? E.g. I'm building lib, that need logging. I want that application will provide instance of KLogger to my lib. If application don't provide it, then some default KLogger should be used. Question is, hot to initialize it, so I don't need to put logger in every class?

If you declare a global

val logger = KotlinLogging.logger {}

you should be able to use it anywhere.

kotlin-logging is a MPP library that uses SLF4J on JVM, SLF4J is a facade to whatever implementation you choose. So I wouldn't be worried about 3 libraries. Does logback-android provide what you need. You can choose to use it with or without kotlin-logging as SLF4J is automatically included with logback. I believe kotlin-logging offer advantages that make logging code efficient and as unintrusive as possible.

I have created a PR ( https://github.com/MicroUtils/kotlin-logging/pull/119 ) for adding support for the Kotlin Native linuxX64 target. Would welcome some feedback, and would like to get some guidance from a Kotlin Native team member on a major design question.

Hey all, is it possible to use just the KLogger interface/facade in a MPP library and let it be manually implemented on each platform? (I have an iOS target that I can't build for because kotlin-logging doesn't support it.)

Hey, is there a way to intercept all the logs to e.g. send them to an Elasticsearch instance etc.?

Hi everybody, I have a small question about performance of

<http://logger.info|logger.info>("blah $foo $bar")

vs

<http://logger.info|logger.info> { "blah $foo $bar" }

. I suppose: 1. in the first case the string template is always constructed 2. in the second one only when the log level is set to make it visible. But there is extra lambda, etc. Is it something I should worry about under a rather intensive load (backend) or it’s not worth optimizing?

2.0.0 is almost ready with kotlin 1.4 support and more platforms and needs feedback Breaking change is a change in the artifact coordinates from

kotlin-logging

to

kotlin-logging-jvm

In order to try it:

repositories {
	maven { url '<https://oss.jfrog.org/artifactory/oss-snapshot-local>' }
}

dependencies {
	compile('io.github.microutils:kotlin-logging-jvm:2.0.0-SNAPSHOT')
}

basic question : I want all my log messages to be pre-pending w/ a specific string, and that string is setup when the logger is created by appending to the end of the existing string. so you kinda create a tree of "child" loggers. not sure if that makes sense. How would i do that using kotlin-logging?

Why are log functions not inline btw? If they were i would not need weird workarounds for suspending functions..

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:

is there anyway to hide/disable the ability to get the default logger? I have a framework where I only want to loggers created by a factory in the framework.

how can i retrieve MDC from a CoroutineContext in a exception handler ? the code looks like so currently

private val exceptionHandler = CoroutineExceptionHandler { context, e -> GlobalScope.launch(MDCContext() + context) {

can i somehow do

context.getCopyOfContextMap()

?

Hi everybody, thought I'd share this small library to write logs to OpenTracing spans https://github.com/fstien/kotlin-logging-opentracing-decorator