Kong HTTP Log Plugin - Sync or Async?


I am starting to evaluate HTTP Log Plugin.

Can someone please explain if the log plugin works in a synchronous fashion i.e an API invocation waits for the http logging to succeed/fail to continue with the response to the client
OR in an asynchronous fashion, i.e irrespective of what happens with the http logging, it continues to give the response to the client.

Or in other words, is it a blocking call or is it more like a netty non blocking call?

From a performance standpoint, this will be a major issue if it’s blocking.


non-blocking., it will not impact your service call.

Thank you for the reply Jeremy. Appreciate it.


Hello, may I ask you a question?
I don’t understand how to use the plugin Http Log,and can’t get a log format as https://docs.konghq.com/hub/kong-inc/http-log/.should i need to do anything else with http-log or httpd server

Not sure the question here? Have you written anything to accept the HTTP payload Kong sends as a log sink?

One quick and dirty way to verify an http behavior would be to stand up a webserver to accept the calls, I am a java dev by nature one easy one is : http://sparkjava.com/documentation

Then send traffic on the endpoint you expose and maybe log the request.body() to std out or something if you need proof its working?