You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adding just one symbol totally ruins MsgPack decoder in Logstash.
In case of Docker logging Logstash is able to wrongly decode first half of packet, incorrectly decodes container_id and then tries to decode remainder of message as MsgPack packet and fails there (because remaining junk has no tag/epochtime/etc fields).
The text was updated successfully, but these errors were encountered:
moved from elastic/logstash#7102
created by @gasparch
When trying to send logs from Docker to Logstash using fluent I've discovered that logstash is not able to parse logs
Same Docker can send logs to Fluentd and they are processed normally. After some debug here is a minimal case that triggers the error.
Logstash 1:5.4.0-1
CentOS 7, kernel 3.10.0-514.6.1.el7.x86_64
Only changed file from default installation is
/etc/logstash/conf.d/config.conf
docker run --rm --name 'containName' --log-driver fluentd --log-opt fluentd-address=xxxxx.4:4000 --log-opt tag="test" busybox /bin/sh -c 'while true; do echo "test"; sleep 1; break; done'
I managed to write minimal code that produces the error:
gem install fluent-logger
irb
and issue commandsFollowing command produces log in Logstash
Following command causes error in Logstash
Adding just one symbol totally ruins MsgPack decoder in Logstash.
In case of Docker logging Logstash is able to wrongly decode first half of packet, incorrectly decodes container_id and then tries to decode remainder of message as MsgPack packet and fails there (because remaining junk has no tag/epochtime/etc fields).
The text was updated successfully, but these errors were encountered: