Wrong class name printed when using LoggingEventBuilder with payload about kotlin-logging HOT 10 CLOSED

Thank you for reporting an issue. See the wiki for documentation and slack for questions.

from kotlin-logging.

The difference seems to be inside LocationAwareKLogger.

Log statements without payload are logged using: org.slf4j.spi.LocationAwareLogger.log(org.slf4j.Marker marker, String fqcn, int level, String message, Object[] argArray, Throwable t)

Log statements with payload are logged using:
org.slf4j.spi.LoggingEventBuilder.log(String message).
LocationAwareKLoggger.logWithPayload seems to correctly set the callerBoundary.

The first thing org.slf4j.spi.DefaultLoggingEventBuilder.log(String message) does is to override the callerBoundary with its own classname.

Therefore I think the bug is inside slf4j not in kotlin-logging.

Maybe leave the issue open until the bug is resolved there ...

from kotlin-logging.

Are you using log4j? There was a related bug there.

from kotlin-logging.

No Im using slf4j-jdk the java util logging.

from kotlin-logging.

Log4j slf4j issue is here for reference: apache/logging-log4j2#1533

from kotlin-logging.

It might be a similar fix.

from kotlin-logging.

Seems like this should be fixed in slf4j 2.0.13. I will try to upgrade.

from kotlin-logging.

Seems like this should be fixed in slf4j 2.0.13. I will try to upgrade.

should be in version 6.0.9.

from kotlin-logging.

When using slf4j version 2.0.13 the correct class name is logged.
@oshai feel free to close the issue.

from kotlin-logging.

Thanks!

from kotlin-logging.