How do I get Ktor to log exception stack traces (occurring inside a route handler) instead of just r...

# ktor

[Zachary Siegel]

How do I get Ktor to log exception stack traces (occurring inside a route handler) instead of just returning them as a response body?

[Zachary Siegel]

get this in response, but nothing in logs sad panda

[Zachary Siegel]

And I'd rather not put a try-catch in every route

[Aleksei Tirman [JB]]

You can configure a logging implementation library for SLF4J on the server, like logback-classic, to log full stack traces. Here is an example of logback.xml file:

<configuration>
<appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
    <encoder>
        <pattern>%d{YYYY-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern>
    </encoder>
</appender>
<root level="trace">
    <appender-ref ref="STDOUT"/>
</root>
<logger name="org.eclipse.jetty" level="INFO"/>
<logger name="io.netty" level="INFO"/>
</configuration>

[Zachary Siegel]

<configuration>
  <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
    <encoder>
      <pattern>%d{YYYY-MM-dd HH:mm:ss.SSS} [%thread] %X{call-id} %-5level %logger{36} - %msg%n</pattern>
    </encoder>
  </appender>
  <root level="INFO">
    <appender-ref ref="STDOUT"/>
  </root>
  <logger name="io.netty" level="INFO"/>
  <logger name="org.quartz" level="DEBUG"/>
</configuration>

[Zachary Siegel]

this is my logback.xml file i have already