# Parsing logs filebeat

**URL:** <https://discuss.elastic.co/t/parsing-logs-filebeat/272011>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [May 3, 2021, 5:55pm UTC](https://discuss.elastic.co/t/parsing-logs-filebeat/272011 "2021-05-03T17:55:52Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mostpha456](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@mostpha456](https://discuss.elastic.co/u/mostpha456)\
**Post date:** [May 3, 2021, 5:55pm UTC](https://discuss.elastic.co/t/parsing-logs-filebeat/272011/1 "2021-05-03T17:55:52Z")

</div>

Hello,  
I m using filebeat to parse my logs  
I have logs of the following format:  
ID: xxx  
Date: xxx  
Message: xxx  
is it possible to send the logs to elasticsearch by adding the fields ID, Date, Message and their values ​​without going through logstash ?

Thank you

---

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [May 4, 2021, 2:04am UTC](https://discuss.elastic.co/t/parsing-logs-filebeat/272011/2 "2021-05-04T02:04:29Z")

</div>

Yes, you'll need to setup a multi line input, see [Manage multiline messages | Filebeat Reference [7.12] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/current/multiline-examples.html#multiline-examples). them add a dissect processor that can parse the message using `\n` to represent the line breaks.

---

<div class="post-metadata">

**Author:** ![mostpha456](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@mostpha456](https://discuss.elastic.co/u/mostpha456)\
**Post date:** [May 5, 2021, 11:42am UTC](https://discuss.elastic.co/t/parsing-logs-filebeat/272011/3 "2021-05-05T11:42:13Z")

</div>

Hello,  
thank you for your answer.  
i m having a dissect\_parsing\_error, l think it s because of the \n, do you have any idea where i can find any exemple of dissect using /n ?  
Thank you

---

<div class="post-metadata">

**Author:** ![legoguy1000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/legoguy1000/32/54301_2.png) [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)\
**Post date:** [May 5, 2021, 12:04pm UTC](https://discuss.elastic.co/t/parsing-logs-filebeat/272011/4 "2021-05-05T12:04:51Z")

</div>

I'll have to find it. There was another post on this forum that people discussed it and that's where I saw the `\n`. I'll see if I can find it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 2, 2021, 2:05pm UTC](https://discuss.elastic.co/t/parsing-logs-filebeat/272011/5 "2021-06-02T14:05:33Z")

</div>

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