Is there a way to add a suffix/tag to logs based on which module/plugin/etc. is doing the logging? R...

# ktor

[Alex Cruise]

Is there a way to add a suffix/tag to logs based on which module/plugin/etc. is doing the logging? Right now it’s always Application

[Aleksei Tirman [JB]]

Could you please explain what log messages are you talking about (on a client or a server)?

[Alex Cruise]

In a server, I’d like to see which module/plugin logged the line

[Alex Cruise]

Ideally without needing to add the tag manually to every slf4j call 🙂

[Alex Cruise]

I guess something like constructing a child logger from the one I got from the environment

[FunkyMuse]

You can tag your path

[Alex Cruise]

slf4j “marker” feature?

[Aleksei Tirman [JB]]

There is a brittle solution to implement your own org.slf4j.Logger where you can retrieve a calling class from the stack trace and log its name or its source file name. That will work on JVM only.

ApplicationEngineEnvironmentReloading.kt: Autoreload is disabled because the development mode is off.
BaseApplicationEngine.kt: Application started in 0.095 seconds.
CallLogging.kt: Application started: io.ktor.server.application.Application@5b3f61ff
BaseApplicationEngine.kt: Responding at <http://0.0.0.0:3333>
server.kt: ewqe
CallLogging.kt: 200 OK: GET - /