-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kafka 0.9+ consumer support #1312
Comments
Input consumer kafka should update the kafka client sarama library and use the new consumer config with sasl ans ssl support. |
If I understand the issue correctly, this is basically just a request to support consumption from Kafka 0.9+ clusters, which comes with the security features mentioned. |
for reference: the shopify sarama library makes a short mention of the difference: https://godoc.org/github.com/Shopify/sarama and confluent wrote a blog post: https://www.confluent.io/blog/tutorial-getting-started-with-the-new-apache-kafka-0-9-consumer-client/ |
An additional benefit of the new consumer (0.9+) is the consumer offsets are stored within the broker cluster and not the zookeeper cluster. This also allows the configuration to directly reference a bootstrap host (any broker in the cluster) instead of the zookeepers for initial connection. |
So after investigating further there are two client libs for the 0.9+ version of Kafka: OfficialCommunityThe official version relies on |
well i tried binary from @seuf, and it works like a charm: |
Closing, support was added in 1.4 |
Proposal:
Kafka supports authentication (GSSAPI since v0.9 and PLAIN(User/PW) since v0.10) and encryption (SSL) between the Kafka cluster and clients.
Current behavior:
The Telegraf Kafka-Consumer can't access secured clusters
Desired behavior:
Telegrafs Kafka-Consumer should be able to read data from secured clusters too.
Therefore it should support SASL_SSL, SASL_PLAINTEXT (with SASL=GSSAPI and SASL=PLAIN)
In other applications dealing with the same issue the application just allows to pass a set of attributes to the underlying Kafka Consumer library.
See the documentation here on which attributes are required: http://docs.confluent.io/3.0.0/kafka/security.html
Use case: [Why is this important (helps with prioritizing requests)]
Since Kafka introduced the security features, there is a move to secured Kafka clusters. Influx Products should keep up with the progress.
The text was updated successfully, but these errors were encountered: