-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Beat via Kafka #5254
Comments
We do not have anything scheduled yet, but this is a valid request. |
is it on the roadmap ? You are pushing Filebeat to ingest logs, but we are unable to connect it to a queue. |
any news about this ? |
News would be great, we are also waitung for this feature. |
Is there a reason that the existing Kafka inputs don't work for this case? What additional functionality are we hoping to get from specifically building a Kafka input for Beats? |
@waab76 We can reuse the Kafka transport infrastructure but need a new Kafka-based input with a Beats codec. We have to find out how the Beats payload looks like. If it's the same binary payload that is used in the lumberjack protocol, we can probably reuse the Beats input's codec. |
Tentatively targeting this for 6.1 |
we use graylog and sidecar to collector application logs,but graylog-server input has been the bottle-neck, so we think it will be better if let Beat input get messages from kafka.
Is there any schedule to develop this feature now?
The text was updated successfully, but these errors were encountered: