You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I have a question regarding call logging in Ktor (1.2.4). When a request comes with 'bad' json, i.e. some fields are missing and deserializaition fails, then with CallLogging feature the bad request message is logged to the default level setup in CallLogging feature configuration. So if I have a default level INFO then I'll see something like this in logs
{
"level": "INFO",
"logger":"Application",
"message":"400 Bad Request: POST - <routing_path>"
}
Is there a way to change the logging level of the failing request?
Even if I do something like this in the CallLogging configuration, the log level is still a default one, i.e. INFO in my case
filter { call ->
val status = call.response.status()?.value
level = Level.WARN
status !in (200..399)
}
The text was updated successfully, but these errors were encountered:
ghost
changed the title
Bad request are logged on default level
Bad request are logged on the default level
Nov 28, 2019
Hi! I have a question regarding call logging in Ktor (1.2.4). When a request comes with 'bad' json, i.e. some fields are missing and deserializaition fails, then with CallLogging feature the bad request message is logged to the default level setup in CallLogging feature configuration. So if I have a default level INFO then I'll see something like this in logs
Is there a way to change the logging level of the failing request?
Even if I do something like this in the CallLogging configuration, the log level is still a default one, i.e. INFO in my case
The text was updated successfully, but these errors were encountered: