# Fielbeat only send line by line instead the whole new log entry at once
**URL:** https://discuss.elastic.co/t/fielbeat-only-send-line-by-line-instead-the-whole-new-log-entry-at-once/41177
**Category:** Beats
**Tags:** filebeat
**Created:** [February 8, 2016, 11:53am UTC](https://discuss.elastic.co/t/fielbeat-only-send-line-by-line-instead-the-whole-new-log-entry-at-once/41177 "2016-02-08T11:53:52Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Pablo\_perez](https://discuss.elastic.co/u/Pablo_perez)
#### Post date: [February 8, 2016, 11:53am UTC](https://discuss.elastic.co/t/fielbeat-only-send-line-by-line-instead-the-whole-new-log-entry-at-once/41177/1 "2016-02-08T11:53:52Z")
Let´s say that I have a cluster where I´m sending logs line from filebeat to logstash.
My problem is that filebeat since send line by line, and in my logstash I have configure that the input codec is json, my logstash is throwing a \_jsonparsefailure since my json as I said in two lines has a wrong format.
Any idea if it is possible send the whole entry log as once and not line by line?. It´s really weird the current behavior of filebeat, I was expecting that If I add a several lines in my log at once, filebeat will send all those at the same time, and not line by line.
Maybe I´m doing something wroing here.
Regards.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [February 8, 2016, 12:04pm UTC](https://discuss.elastic.co/t/fielbeat-only-send-line-by-line-instead-the-whole-new-log-entry-at-once/41177/2 "2016-02-08T12:04:21Z")
Filebeat generally treats each line in the log file as a separate event, but if you are using the latest version you can configure it to [assemble records spanning multiple lines](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-configuration-details.html#multiline) using regular expressions.
---
### Author:  [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [February 9, 2016, 12:49am UTC](https://discuss.elastic.co/t/fielbeat-only-send-line-by-line-instead-the-whole-new-log-entry-at-once/41177/3 "2016-02-09T00:49:40Z")
most log-shippers work line by line. filebeat has a multiline support for connecting multiple lines into one event.
Can you configure your application to not pretty-print the json?
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [February 9, 2016, 7:53pm UTC](https://discuss.elastic.co/t/fielbeat-only-send-line-by-line-instead-the-whole-new-log-entry-at-once/41177/4 "2016-02-09T19:53:32Z")
> I was expecting that If I add a several lines in my log at once, filebeat will send all those at the same time, and not line by line.
File systems don't work that way. Filebeat has _no way_ of knowing that the application writing to the log wrote two lines in one "transaction".
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 9:55pm UTC](https://discuss.elastic.co/t/fielbeat-only-send-line-by-line-instead-the-whole-new-log-entry-at-once/41177/5 "2017-07-05T21:55:53Z")