file output ignores codec


Using following config:

Expected: each event written in 3 different formats.
Actual result: all written in (new) json format.

This snippet from /lib/logstash/outputs is probably the bad guy:

Maybe output plugins not supporting codecs should not accept the codec parameter? It is currently part of the base class, which is probably a bad thing.

Bit of context: I am trying to upgrade Logstash from 1.1.13 (to 1.3.2) without wanting to upgrade ES/Kibana. So I need a working oldlogstashjson setup.


Richard Pijnenburg
January 14, 2014, 3:39 PM

Ps. why would you need to write out into the old format.
You could also read in data from the old format and export that into the new?
all codecs are defo supported in the inputs.

Renzo Toma (moved to gchat)
January 14, 2014, 3:41 PM

In 1.3.2 only a few output plugins have codec support. Here is a list:

All others output plugins do not have codec support.

Renzo Toma (moved to gchat)
January 14, 2014, 3:44 PM

Our current ES clusters have ~4TB of logging in the old format. I really not want to convert all those events. And I really not want to upgrade logstash, ES and Kibana in one big-bang.

If you can suggest a better way of upgrading these 3 packages I love to hear any suggestions.

Jason Kendall
April 17, 2014, 2:37 PM

Confirming this against 1.4.0

Testing with compress_spooler outputs with no codec applied.

Philippe Weber
March 17, 2015, 12:00 PM


Logstash Developers


Renzo Toma (moved to gchat)

Affects versions