JSON codec creating unreadable data


(Sjaak) #1

Hi,

For whatever reason the JSON codec suddenly is coding messages in such a way that only the first message in a file is readable.

The forum doesn't allow uploading files so I can't attach the actual file but the file that is uploaded to my S3 is strange. It looks normal when opening it but with notepad++ I can't use any enters. If I copy/paste everything to a new file I can.

{"@timestamp":"2018-01-19T10:51:05.000Z","error":"error1"}{"@timestamp":"2018-01-19T10:51:06.000Z","hdg":"139.93"}{"lon":"22222.2222,W","speed":"16.06","@timestamp":"2018-01-19T10:51:11.000Z","trck_angl":"138.01","lat":"1111.1111,N"}{"@timestamp":"2018-01-19T10:51:19.000Z","error":"error2"}{"@timestamp":"2018-01-19T10:51:23.000Z","EbNo":"1.2"}

ouput

 s3 {
     codec => "json"
     access_key_id => "secret"
     secret_access_key => "secret"
     region => "eu-west-2"
     bucket => "secret"
     time_file => 1

   }

input

input {
  s3 {
     access_key_id => "secret"
     secret_access_key => "secret"
     region => "eu-west-2"
     bucket => "secret"
     codec => "json"
  }
}

I also got a file output with no codec set and output created by that file works fine if I use a file input to read the data.

I've already updated logstash and plugins to the latest version. I have absolutely no clue what to do as I cannot see any errors generated anywhere, the data is just ignored.

I have no idea how to proceed or troubleshoot the issue. Any help would be greatly appreciated.


(Sjaak) #2

Looks like changing the output codec to json_lines and leaving the input codec as json solved the issue.


(system) #3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.