Elastic search index is getting created as BSON instead of JSON

[nagarajanj (Naga)]

We are using logstash to move the data b/w mongo db and elastic.. however the
data is getting created as BSON instead of JSON..

I keep getting all the data in a "log_entry" field as one big string.

when we do the same from S3 to elastic using logstash , the data is coming correctly as the JSON.

Our issue is exactly same as the below reported issue..

Formatting issues with parsing JSON from MongoDB

I am trying to parse JSON (from MongoDB) to Kibana through Logstash. I keep getting all the data in a "log_entry" field. This field does not exist in my data but rather is being created by Logstash. In my CONF file, I have my filter empty. I have tried adding JSON with source as a specific field but that does not work either. Any ideas? [43%20PM]

Please advise..

[Badger]

@nagarajanj

I keep getting all the data in a "log_entry" field as one big string.

That is what the mongodb input does. That is not an elastic supported input.

If I had to deal with that I would install the bson gem (see here for how to do that and why it is a bad idea), then repurpose some IBM code to do the BSON => JSON conversion in a ruby filter.

If you can get that working it would be interesting to see.

[nagarajanj (Naga)]

Thanks a lot for your inputs..let me try this..