In the world of DevOps, metric collection, log centralization and analysis Apache Kafka is the most commonly used middleware. More specifically, it is used as a fast, persistent queue between data sources like log shippers and the storage that makes our data, such as logs, searchable. In this post we’ll use the log shipping use case and Elasticsearch as logs storage, but the same principles apply to other forms of data. We assume that the data that comes to Kafka is already JSON formatted, so please keep that in mind. We also describe how to ship logs to Sematext Logs at the very end.

Looking for a hosted Elasticsearch as a Service? Check Sematext Cloud! Get scheduled reports, alerting, anomaly detection, ChatOps integration, and more.

Plus, Sematext Cloud is a monitoring AND log management solution in one. See all features

Most systems we see in our logging consulting practise use Kafka to achieve high availability, fault tolerance, and expose incoming data to various consumers and have ingestion pipeline that looks a bit like this:

There are lots of options when it comes to choosing the right log shipper and getting data into Kafka. We can use Logstash or one of several Logstash alternatives, such as rsyslog, Filebeat, Logagent, or anything that suits our needs – the lighter the better.

Once you figure out how to get data into Kafka the question how to get it out of Kafka and into something like Elasticsearch inevitably comes up. The answer is often “it depends”. You could implement your own solution on top of Kafka API – a consumer that will do whatever you code it to do. However, that is time consuming, requires at least basic knowledge of Kafka and Elasticsearch, is error prone and finally requires us to spend time on code management.

Looking for an easy way to manage Kafka logs?

Built on ELK, Sematext Logs offers an easy way to monitor your logs and ensure peak performance of your cluster!

Learn more See plans

No credit card required – Be up and running in no time. Built on ELK, Sematext Logs offers an easy way to monitor your logs and ensure peak performance of your cluster!

Instead, we could use one of the ready to use solutions like Logstash which is powerful and versatile, but if we do that we still have to care about fault tolerance and single point of failure. So, if we are seeking a solution that is less powerful when it comes to processing capabilities, but comes with out of the box distribution based on already present system component – Kafka Connect Elasticsearch may be a good thing to look at.

Looking to replace Splunk or a similar commercial solution with Elasticsearch, Logstash, and Kibana (aka, “ELK stack” or “Elastic stack”) or an alternative logging stack? In this eBook you’ll find useful how-to instructions, screenshots, code, info about structured logging with rsyslog and Elasticsearch, and more.

Download yours.

Introducing Kafka Connect for Elasticsearch

Current Kafka versions ship with Kafka Connect – a connector framework that provides the backbone functionality that lets you connect Kafka to various external systems and either get data into Kafka or get it out. It makes it possible to quickly develop connectors that move data to or from Kafka and can leverage Kafka distributed capabilities making data flow fault tolerant and highly available. What’s more, the connector framework provides an easy to use REST API for retrieval of information about connectors, updating configuration, and managing connectors themselves. It is also highly configurable, works in both standalone and distributed mode and finally, it is easy to use.

One of the available connectors is Kafka Connect Elasticsearch which allows sending data from Kafka to Elasticsearch. It uses Jest, which is a HTTP based Elasticsearch client library, which should avoid incompatibilities with different Elasticsearch versions, at least minor one. In this blog post we will see how to quickly set up this connector to send data from a Kafka topic to Elasticsearch.

Kafka Connect Elasticsearch Test Setup

Our test setup will be very simple: one Zookeeper instance, one Kafka broker, and one Elasticsearch node, all installed on a single machine and listening on the following ports:

Zookeeper – 2181

Kafka – 9092

Elasticsearch – 9200

We assume that we already have a logs topic created in Kafka and we would like to send data to an index called logs_index in Elasticsearch. To simplify our test we will use Kafka Console Producer to ingest data into Kafka.

We will use Elasticsearch 2.3.2 because of compatibility issues described in issue #55 and Kafka 0.10.0. We use Kafka 0.10.0 to avoid build issues.

Building Elasticsearch Connector

When using Kafka Connect Elasticsearch, you can download one of the releases or build it yourself.

We will focus on building the package, just so you know how easy that can be done and you can use the newest version of the connector with your Kafka version. You’ll need Maven.

Clone the appropriate branch of the project:

$ git clone -b 0.10.0.0 https://github.com/confluentinc/kafka-connect-elasticsearch.git

Build it:

$ cd kafka-connect-elasticsearch $ mvn clean package

Once Maven downloads needed libraries, compiles and builds the code you should see a message similar to the following one:

[INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 24.825 s [INFO] Finished at: 2017-02-27T15:03:51+01:00 [INFO] Final Memory: 39M/558M [INFO] ------------------------------------------------------------------------

That means that the connector has been built and we can find it in the target/kafka-connect-elasticsearch-3.2.0-SNAPSHOT-package/share/java/kafka-connect-elasticsearch/ directory. The final thing that we need to do is copying all the libraries from that directory to Kafka libs directory. Keep in mind that you have to do this on all your servers that will run the connector. For example, if you plan on running the connector in distributed mode it would be good to have the libraries on all your Kafka brokers.

Configuring Elasticsearch Connector

Before running Kafka Connect Elasticsearch we need to configure it. We’ll create elasticsearch-connect.properties with the following content:

name=elasticsearch-sink connector.class=io.confluent.connect.elasticsearch.ElasticsearchSinkConnector tasks.max=1 topics=logs topic.index.map=logs:logs_index connection.url=http://localhost:9200 type.name=log key.ignore=true schema.ignore=true

This file will be provided as one of the configuration files and will define the behavior of the connector. We said that we wanted to use io.confluent.connect.elasticsearch.ElasticsearchSinkConnector sink, which will be responsible for sending data to Elasticsearch and we set its name to elasticsearch-sink. The name should be unique for a given connector. We also said that we want a single task to be created for that connector to work (tasks.max property), but Kafka may create fewer tasks if it can’t achieve the specified level of parallelism. We want to read data from the logs topic (keep in mind that we can specify multiple topics as the source of the data using the topics property) and that data from the logs topics should be placed in an index called logs_index (using the topic.index.map) property. We want to use local Elasticsearch instance (specified using connection.url) and the data should use the log type (because of the value of the type.name property). Finally, we told Kafka Connect to ignore key and schema by using the key.ignore=true and schema.ignore=true, because we assume that we will use the templates in Elasticsearch to control the data structure and analysis, which is a good practice in general.

Running Kafka Connect Elasticsearch in Standalone Mode

To run the connector in standalone mode we will use the connect-standalone.sh which is provided with Kafka and can be found in the bin directory. It requires two configuration files, the one that we already created and another one, which we will call connect-standalone.properties and which will have the following contents:

bootstrap.servers=localhost:9092 key.converter=org.apache.kafka.connect.json.JsonConverter value.converter=org.apache.kafka.connect.json.JsonConverter key.converter.schemas.enable=false value.converter.schemas.enable=false internal.key.converter=org.apache.kafka.connect.json.JsonConverter internal.value.converter=org.apache.kafka.connect.json.JsonConverter internal.key.converter.schemas.enable=false internal.value.converter.schemas.enable=false offset.storage.file.filename=/tmp/connect.offsets offset.flush.interval.ms=10000

It defines Kafka brokers list, key and value converters, whether schemas should be used, and so on.

After we are done with the configuration, to run the connector we just execute the following command:

$ bin/connect-standalone.sh config/connect-standalone.properties config/elasticsearch-connect.properties

This will start the connector as a separate JVM process on the same server that Kafka is started and any data you put in the defined topic in Kafka will be sent to Elasticsearch. However – we have a single point of failure here – a single instance of the connector. We can run Kafka Connect Elasticsearch connector in distributed mode to leverage the distributed nature of Kafka itself, so let’s do that next.

Running Kafka Connect Elasticsearch in Distributed Mode

Running Kafka Connect Elasticsearch in a standalone mode is fine, but it lacks the main benefits of using Kafka Connect – leveraging the distributed nature of Kafka, fault tolerance, and high availability. The difference in running the connector in standalone and distributed mode is where Kafka Connect stores the configuration, how it assigns where the work should be done, where to store the offsets and tasks statuses.

Let’s start with the configuration. We will store it in the connect-distributed.properties file:

bootstrap.servers=localhost:9092 key.converter=org.apache.kafka.connect.json.JsonConverter value.converter=org.apache.kafka.connect.json.JsonConverter key.converter.schemas.enable=false value.converter.schemas.enable=false internal.key.converter=org.apache.kafka.connect.json.JsonConverter internal.value.converter=org.apache.kafka.connect.json.JsonConverter internal.key.converter.schemas.enable=false internal.value.converter.schemas.enable=false offset.flush.interval.ms=10000 group.id=connect-cluster offset.storage.topic=connect-offsets config.storage.topic=connect-configs status.storage.topic=connect-status

We already covered some of the properties shown above. The new properties are:

group.id – the identifier of the cluster for Kafka Connect group. It should be unique and must not interfere with consumers reading data from the given Kafka cluster.

offset.storage.topic – the name of the topic Kafka Connect will use to store offsets. The idea behind this topic is to have many partitions, be replicated and configured for compaction.

config.storage.topic – the name of the topic Kafka Connect will use to store configuration. The idea behind the topic configuration is to have a single partition and be highly replicated.

status.storage.topic – the name of the topic Kafka Connect will use to store work status. It should have multiple partitions, replicas and be compacted.

Once we have such configuration, we can start the connector in distributed mode:

$ bin/connect-distributed.sh config/connect-distributed.properties

You may have noticed one difference compared to running Kafka Connect in standalone mode – we didn’t provide the configuration for the connector itself. This is not a mistake! When using Kafka Connect in distributed mode we need to create connectors using the REST API. Let’s not focus on this now, though, as we’ll get to that a bit later.

So what is the difference between standalone and distributed Kafka Connect mode? Both end up running in their own JVM process as Kafka Connect clients and as such they both need access to Kafka libraries, which is why running them on Kafka brokers makes sense. The major difference is in how the job is executed. In the standalone mode the work is performed in a single process, while in distributed mode it is shared by all available Kafka Connect client instances running along Kafka broker instances. Another difference is in where the client stores its configuration – in distributed mode it is stored inside Kafka, in its own topics defined by the configuration (using the offset.storage.topic, config.storage.topic and status.storage.topic properties). In standalone mode offsets are stored in the configuration file specified by the offset.storage.file.filename property. So, if you have your Kafka Connect Elasticsearch running in distributed mode you can leverage multiple instances of it and either create multiple tasks (using the tasks.max property) or rely on failover that comes for free if you are running Kafka Connect in distributed mode and you have multiple instances of Kafka Connect Elasticsearch started. For example, if you set max.tasks=1 and have 2 instances of Kafka Connect started, than when one fails, the other will get the task to execute. This, of course, helps avoid Kafka Consumer Lag.

Troubleshooting

There are two places to look at when troubleshooting: Kafka broker logs and Kafka client logs. In Kafka broker logs you’ll find issues with classes not being found and Kafka related errors. Kafka client logs hold info from Kafka client that is started when you launched Kafka Connect Elasticsearch. By default both of them are available on standard output, but you can configure that using properties file (log4j.properties for Kafka and connect-log4j.properties for Kafka Connect). You also can monitor Kafka and monitor Elasticsearch with Sematext Monitoring or other Kafka monitoring tools.

Sending Example Data

Now we can produce some data. Keep in mind that we assumed that the data stored in Kafka will be in JSON format, so we need to stick to that. Let’s start the simple console producer that comes with Kafka:

$ bin/kafka-console-producer.sh --topic logs --broker-list localhost:9092

And start sending JSON logs, such as these:

{"name":"Test log", "severity": "INFO"} {"name":"Test log 2", "severity": "WARN"}

To test that everything is working, we just need to run a simple Elasticsearch query:

$ curl -XGET 'localhost:9200/logs_index/_search?pretty'

In return we should get the following response:

{ "took" : 3, "timed_out" : false, "_shards" : { "total" : 5, "successful" : 5, "failed" : 0 }, "hits" : { "total" : 3, "max_score" : 1.0, "hits" : [ { "_index" : "logs_index", "_type" : "true", "_id" : "logs+0+2", "_score" : 1.0, "_source" : { "severity" : "WARN", "name" : "Test log 2" } }, { "_index" : "logs_index", "_type" : "true", "_id" : "logs+0+1", "_score" : 1.0, "_source" : { "severity" : "INFO", "name" : "Test log" } } ] } }

As you can see everything works as it should. With very little effort we got ourselves a quick and easy way of indexing data from our Kafka cluster to Elasticsearch. What’s more, this is not only simple shipping, but really distributed indexing that handles failover and fault tolerance out of the box, without us needing to do anything apart from connector configuration.

Kafka Connect REST API

By default the REST API service runs on port 8083. You can check if it is running, by executing a simple curl command:

$ curl 'localhost:8083'

In response you will get the version and the commit hash of the build:

{"version":"0.10.2.0","commit":"576d93a8dc0cf421"}

We can retrieve the list of running connectors:

$ curl 'localhost:8083/connectors'

For example, in case of running our Elasticsearch connector in standalone mode the response will be as follows:

["elasticsearch-sink"]

To retrieve the list of connector plugins installed in the Kafka cluster:

$ curl 'localhost:8083/connector-plugins'

The response looks as follows:

[{"class":"io.confluent.connect.elasticsearch.ElasticsearchSinkConnector"},{"class":"org.apache.kafka.connect.file.FileStreamSinkConnector"},{"class":"org.apache.kafka.connect.file.FileStreamSourceConnector"}]

To retrieve the configuration:

$ curl 'localhost:8083/connectors/elasticsearch-sink/config'

Which will result in the following response in our case:

{"connector.class":"io.confluent.connect.elasticsearch.ElasticsearchSinkConnector","type.name":"true","topics":"logs","tasks.max":"1","topic.index.map":"logs:logs_index","name":"elasticsearch-sink","connection.url":"http://localhost:9200","key.ignore":"true","schema.ignore":"true"}

Check the status of the given connector:

$ curl 'localhost:8083/connectors/elasticsearch-sink/status'

Retrieve tasks running by a given connector:

$ curl 'localhost:8083/connectors/elasticsearch-sink/tasks

Of course, this is not everything and we are not limited to retrieval part of the API. We can add new connectors by running a HTTP POST command to the /connectors end-point with the name and configuration parameters in the body (as a JSON object). For example:

$ curl -XPOST -H 'Content-type:application/json' 'localhost:8083/connectors' -d '{ "name" : "second_es_sink", "config" : { "connector.class" : "io.confluent.connect.elasticsearch.ElasticsearchSinkConnector", "tasks.max" : "1", "topics" : "logs", "topic.index.map" : "logs:logs_index", "connection.url" : "http://localhost:9200", "type.name" : "true", "key.ignore" : "true", "schema.ignore" : "true" } }'

We can pause, resume and restart connector if failed:

$ curl -XPUT 'localhost:8083/connectors/elasticsearch-sink/pause' $ curl -XPUT 'localhost:8083/connectors/elasticsearch-sink/resume' $ curl -XPOST 'localhost:8083/connectors/elasticsearch-sink/restart'

Please keep in mind that the restart uses POST HTTP verb, while the pause and resume use PUT HTTP verb.

Finally, we can remove a given connector using DELETE HTTP verb and providing the name of the connector:

$ curl -XDELETE 'localhost:8083/connectors/second_es_sink'

If you want to read about all the options regarding Kafka Connect REST API, please refer to documentation available at http://kafka.apache.org/documentation.html#connect_rest.

Sending the Data to Sematext Logs

If you are one of our happy Sematext users you can use Kafka Connect Elasticsearch to ship logs from your Kafka to Sematext. You can use either the standalone or distributed mode, just as described above. The only thing you need to change in your configuration are the topic.index.map and connection.url properties.

The topic.index.map property needs to map the topic name to your Logs App token:

topic.index.map=logs:your-logs-app-token-here

The connection.url property needs to be pointed to the Sematext Logs ingestion endpoint:

The full standalone configuration would then look as follows:

name=logsene-sink connector.class=io.confluent.connect.elasticsearch.ElasticsearchSinkConnector tasks.max=1 topics=logs topic.index.map=logs:your-logs-app-token-here key.ignore=true schema.ignore=true connection.url=https://logsene-receiver.sematext.com:80 type.name=log

Once you have that done you can run the connector in standalone mode. Setting the distributed mode to work with Sematext is also simple, the only thing you need to do is run the following command which uses the Kafka Connect REST API:

$ curl -XPOST -H 'Content-type:application/json' 'localhost:8083/connectors' -d '{ "name" : "logsene-sink", "config" : { "connector.class" : "io.confluent.connect.elasticsearch.ElasticsearchSinkConnector", "tasks.max" : "1", "topics" : "logs", "topic.index.map" : "logs:your-logs-app-token-here", "connection.url" : "https://logsene-receiver.sematext.com:80", "type.name" : "true", "key.ignore" : "true", "schema.ignore" : "true" } }'

And that’s it! You can ship your logs from your Kafka to Sematext without needing to run additional log shippers, only Kafka Connect for Elasticsearch.

Interested in a solution that can ensure top-notch security for your cluster?

With Sematext Logs you get scheduled reports, alerting, anomaly detection to help you avoid and prevent any kind of threat.

Get 30-days free trial! See our plans

No credit card required – Get started in seconds. With Sematext Logs you get scheduled reports, alerting, anomaly detection to help you avoid and prevent any kind of threat.

Summary

If you are looking for a quick, fault tolerant and efficient way of pushing data from your Kafka cluster to Elasticsearch or Sematext, or any of the other supported integrations, Kafka Connect may be a good way to go. Apart from leveraging the distributed nature of Kafka and the API, it also provides simple transformation logic making it a very versatile tool for data export. Keep an eye on the next post that will cover how to use the mentioned transformations and more.

your Quick Guide to Logging Basics Don’t forget to download

Share Twitter

Facebook

LinkedIn

Reddit

Email

