CODEWITHSUNDEEP
kongelkkong-plugin
DevSay
DevSay

Reputation: 1176

Best logging plugin of Kong API gateway to utilise existing ELK stack log

Can anyone help me to choose one Kong API Gateway logging plugin from all available options like Tcp Log, Udp Log, Http Log, File Log, Syslog, Statsd, Loggly, etc which can utilize the existing ELK stack log?

Upvotes: 3

Views: 6029

Answers (1)

Philipp
Philipp

Reputation: 510

I made experiences with the file-log, tcp-log and http-log plugin. All worked quite well for us in terms of the actual logging functionality. The main decision driver was the tech stack we used:

  • file-log: We deployed Kong on OpenShift. As OpenShift has a built-in EFK stack and pushes all standard out via Fluentd to ElasticSearch, we wrote our Kong logs to a named pipe ("FIFO file") and made the Docker container to continually print that file to stdout. Kind of a workaround but it worked very well for our use case.
  • tcp-log/http-log: We additionally had a requirement to send the logs to an external ELK stack. For this use case we used the tcp-log plugin. We later switched to http-log as it additionally has a built-in basic auth feature, so you can transfer your logs to an publicly available endpoint with authentication. Both plugins sent the logs to logstash which listened to either a tcp or http port.

I hope this helps you choosing a logging plugin according to your needs.

Upvotes: 5

Related Questions