Skip to main content
Version: 2.5




kafka-logger is a plugin which works as a Kafka client driver for the ngx_lua nginx module.

This will provide the ability to send Log data requests as JSON objects to external Kafka clusters.

This plugin provides the ability to push Log data as a batch to you're external Kafka topics. In case if you did not receive the log data don't worry give it some time it will automatically send the logs after the timer function expires in our Batch Processor.

For more info on Batch-Processor in Apache APISIX please refer. Batch-Processor


broker_listobjectrequiredAn array of Kafka brokers.
kafka_topicstringrequiredTarget topic to push data.
keystringoptionalUsed for partition allocation of messages.
timeoutintegeroptional3[1,...]Timeout for the upstream to send data.
namestringoptional"kafka logger"A unique identifier to identity the batch processor.
meta_formatenumoptional"default"["default","origin"]default: collect the request information with default JSON way. origin: collect the request information with original HTTP request. example
batch_max_sizeintegeroptional1000[1,...]Set the maximum number of logs sent in each batch. When the number of logs reaches the set maximum, all logs will be automatically pushed to the Kafka service.
inactive_timeoutintegeroptional5[1,...]The maximum time to refresh the buffer (in seconds). When the maximum refresh time is reached, all logs will be automatically pushed to the Kafka service regardless of whether the number of logs in the buffer reaches the set maximum number.
buffer_durationintegeroptional60[1,...]Maximum age in seconds of the oldest entry in a batch before the batch must be processed.
max_retry_countintegeroptional0[0,...]Maximum number of retries before removing from the processing pipe line.
retry_delayintegeroptional1[0,...]Number of seconds the process execution should be delayed if the execution fails.
include_req_bodybooleanoptionalfalse[false, true]Whether to include the request body. false: indicates that the requested body is not included; true: indicates that the requested body is included.

examples of meta_format#

  • default:

  • origin:

    GET /hello?ab=cd HTTP/1.1host: localhostcontent-length: 6connection: close


The message will write to the buffer first. It will send to the kafka server when the buffer exceed the batch_max_size, or every buffer_duration flush the buffer.

In case of success, returns true. In case of errors, returns nil with a string describing the error (buffer overflow).

Sample broker list#

This plugin supports to push in to more than one broker at a time. Specify the brokers of the external kafka servers as below sample to take effect of this functionality.

{    "":9092,    "":9093}

How To Enable#

The following is an example on how to enable the kafka-logger for a specific route.

curl -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '{    "plugins": {       "kafka-logger": {           "broker_list" :             {               "":9092             },           "kafka_topic" : "test2",           "key" : "key1",           "batch_max_size": 1,           "name": "kafka logger"       }    },    "upstream": {       "nodes": {           "": 1       },       "type": "roundrobin"    },    "uri": "/hello"}'

Test Plugin#


$ curl -i 200 OK...hello, world

Disable Plugin#

Remove the corresponding json configuration in the plugin configuration to disable the kafka-logger. APISIX plugins are hot-reloaded, therefore no need to restart APISIX.

$ curl  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d value='{    "methods": ["GET"],    "uri": "/hello",    "plugins": {},    "upstream": {        "type": "roundrobin",        "nodes": {            "": 1        }    }}'