documentation for codec default value is always "plain" (not "line" for inputs/tcp)
Description
Gliffy Diagrams
Activity
Show:

Tal Levy February 6, 2015 at 11:39 PM
We have updated docs for Logstash 1.5
I will close this ticket here in JIRA and migrate checks for this in Github issues

Bernd Eckenfels May 9, 2014 at 2:25 AMEdited
Seems to be an issue for other inputs as well (rabbitmq with json instead of plain - but in that case it is not using "default")
https://github.com/elasticsearch/logstash/blob/aeb691b7b1348cf2473820951c3ab9b423d1b306/lib/logstash/inputs/rabbitmq.rb#L107 vs
http://logstash.net/docs/1.4.1/inputs/rabbitmq#codec
Won't Fix
Details
Details
Assignee

Reporter

Affects versions
Created May 8, 2014 at 2:53 AM
Updated February 6, 2015 at 11:40 PM
Resolved February 6, 2015 at 11:40 PM
On the documentation page for
inputs/tcp
it states that the default codec isplain
. For this input theline
codec is however used (I noticed this, because when usingmultiline
it breaks at it will not collect single chars into lines).I am not sure how that part of the documentation is generated, I thought I can fix a comment in tcp.rb to be done, but there is none for
default :codec "line"