Ktor 1.6.7 Help

Call logging

Ktor provides the capability to log application events using the SLF4J library. You can learn about general logging configuration from the Logging topic.

The CallLogging plugin (previously known as feature) allows you to log incoming client requests.

Install CallLogging

To install the CallLogging plugin, pass it to the install function in the application initialization code. Depending on the way used to create a server, this can be the embeddedServer function call ...

import io.ktor.features.* // ... fun main() { embeddedServer(Netty, port = 8080) { install(CallLogging) // ... }.start(wait = true) }

... or a specified module.

import io.ktor.features.* // ... fun Application.module() { install(CallLogging) // ... }

Configure logging settings

You can configure CallLogging in multiple ways: specify a logging level, filter requests based on a specified condition, customize log messages, and so on. You can see the available configuration settings at CallLogging.Configuration.

Set the logging level

By default, Ktor uses the Level.TRACE logging level. To change it, use the level property:

install(CallLogging) { level = Level.INFO }

Filter log requests

The filter property allows you to add conditions for filtering requests. In the example below, only requests made to /api/v1 get into a log:

install(CallLogging) { filter { call -> call.request.path().startsWith("/api/v1") } }

Customize a log message format

By using the format function, you can put any data related to a request/response into a log. The example below shows how to log a response status, a request HTTP method, and the User-Agent header value for each request.

install(CallLogging) { format { call -> val status = call.response.status() val httpMethod = call.request.httpMethod.value val userAgent = call.request.headers["User-Agent"] "Status: $status, HTTP method: $httpMethod, User agent: $userAgent" } }

You can find the full example here: logging.

Put call parameters in MDC

The CallLogging plugin supports MDC (Mapped Diagnostic Context). You can put a desired context value with the specified name to MDC using the mdc function. For example, in the code snippet below, a name query parameter is added to MDC:

install(CallLogging) { mdc("name-parameter") { call -> call.request.queryParameters["name"] } }

You can access the added value during an ApplicationCall lifetime:

import org.slf4j.MDC // ... MDC.get("name-parameter")
Last modified: 09 September 2021