Events shipped by lumberjack are agitated about logstash-forwarder HOT 4 CLOSED

I'm not sure if it's related, but facing somehow the same issue. Using logstasher, lumberjack shipper, logstash indexer, elasticsearch and kibana 3. Solved by using logstash 1.1.13 too as above.

My output:

output received {:event=>#<LogStash::Event:0xa7046e @cancelled=false, @DaTa={"message"=>"{"@source":"unknown","@tags":["request"],"@fields":{"method":"GET","path":"/users/sign_in","format":"/","controller":"devise/sessions","action":"new","status":200,"duration":206.78,"view":20.1,"ip":"61.xx.xx.xxx","route":"devise/sessions#new","parameters":""},"@timestamp":"2013-10-17T19:31:07.925863+00:00"}", "@timestamp"=>"2013-10-17T19:31:08.817Z", "@Version"=>"1", "type"=>"syslog", "file"=>"//path/../../....", "host"=>"xxxxxxxx", "offset"=>"15742693"}>, :level=>:info}
{
"message" => "{"@source":"unknown","@tags":["request"],"@fields":{"method":"GET","path":"/users/sign_in","format":"/","controller":"devise/sessions","action":"new","status":200,"duration":206.78,"view":20.1,"ip":"61.xx.xx.xxx","route":"devise/sessions#new","parameters":""},"@timestamp":"2013-10-17T19:31:07.925863+00:00"}",
"@timestamp" => "2013-10-17T19:31:08.817Z",
"@Version" => "1",
"type" => "syslog",
"file" => "/path/../../....",
"host" => "xxxxxxxxxxx",
"offset" => "15742693"

It seems that I can get my fields to show up, unless I revert back to 1.1.13. Any help will be much appreciate it.

from logstash-forwarder.

Is this still an issue?

from logstash-forwarder.

Well, I'm still using 1.1.13, I didn't try installing a newer version again since the system is stable and I don't want to brake it. I wonder the same, is this fixed on the newest version?

from logstash-forwarder.

In truth, I'm not sure I ever understood the reported problem. I haven't heard of anyone reporting it similar. Will close> We can reopen later if it's still a problem on a recent release of lsf/logstash.

from logstash-forwarder.