-
Notifications
You must be signed in to change notification settings - Fork 23
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
fluent codec doesn't work with latest version of fluentd #2
Comments
Thanks for working on a patch! To be honest, I kind of wrote this thing assuming fluentd's protocol wasn't going to change much. I don't remember much about writing it other than it worked when I wrote and tested it. If there's interest in improving this plugin, keep in mind that we'll want backwards compatibility with the existing codec. |
I'm trying to figure this out, are you saying that on the latest version the data is like this: [
"foobar",
[
[1437717520, { "foo" => "bar" }],
[1437717520, { "foo" => "bar" }]
]
] I can't see how this is possible here for example https://github.com/fluent/fluent-logger-ruby/blob/master/lib/fluent/logger/logger_base.rb#L25 |
Logstash fluentd codec support is currently broken: ref logstash-plugins/logstash-codec-fluent#2 ref logstash-plugins/logstash-codec-fluent#5 until that work is complete testing the log driver against logstash will not be successful.
One issue is that the msgpack format has changed; there is a new code for the type STR8, and your msgpack reference is out of date. |
Is there any progress here? I have similar issue, trying to send logs from docker (using docker log driver) to LS seems like fluent codec is not usable, and this issue is 2yr old |
I've registered patches to handle |
Hi,
Using logstash with a tcp input and the fluent coded, with fluentd configured to send log messages to it, actually doesn't work. It looks like the fluent message format might have been changed at some point.
This is testing with fluentd 0.12
If I modify fluent.rb decode method to look something like
Then logastash does work correctly again
The text was updated successfully, but these errors were encountered: