# Parse JSON data with filebeat

**URL:** <https://discuss.elastic.co/t/parse-json-data-with-filebeat/80008>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [March 25, 2017, 8:08pm UTC](https://discuss.elastic.co/t/parse-json-data-with-filebeat/80008 "2017-03-25T20:08:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tudor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tudor/32/3753_2.png) [@tudor](https://discuss.elastic.co/u/tudor)\
**Post date:** [March 27, 2017, 10:57am UTC](https://discuss.elastic.co/t/parse-json-data-with-filebeat/80008/2 "2017-03-27T10:57:33Z")

</div>

Are the JSON objects written as one per line? The multiline configuration seems to indicate that are not. In general, I'd recommend:

- configuring logrus to output one object per line
- remove the multiline configuration
- Use the [json decoding](https://www.elastic.co/guide/en/beats/filebeat/5.2/configuration-filebeat-options.html#config-json) at the prospector level, instead of the processor

See, for example, this [blog post](https://www.elastic.co/blog/structured-logging-filebeat) on the topic.

---

_[View the full topic](https://discuss.elastic.co/t/parse-json-data-with-filebeat/80008)._