# Remove \\n Characters in Filebeat

**URL:** <https://discuss.elastic.co/t/remove-n-characters-in-filebeat/94544>\
**Category:** Beats\
**Created:** [July 25, 2017, 9:35pm UTC](https://discuss.elastic.co/t/remove-n-characters-in-filebeat/94544 "2017-07-25T21:35:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmtd](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dmtd](https://discuss.elastic.co/u/dmtd)\
**Post date:** [July 25, 2017, 9:35pm UTC](https://discuss.elastic.co/t/remove-n-characters-in-filebeat/94544/1 "2017-07-25T21:35:07Z")

</div>

Removing the content of this topic because it is not an elastic issue.

But for anyone else who comes across this:  
Logs should be written to disk with `\n` for new lines, not `\\n`, and Kibana will read appropriately.

---

<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:** [July 26, 2017, 9:06am UTC](https://discuss.elastic.co/t/remove-n-characters-in-filebeat/94544/2 "2017-07-26T09:06:05Z")

</div>

Filebeat doesn't have support for string replacement, but you can do it either with Ingest Node ([gsub processor](https://www.elastic.co/guide/en/elasticsearch/reference/master/gsub-processor.html)), or with Logstash.

---

<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:** [August 15, 2017, 9:35pm UTC](https://discuss.elastic.co/t/remove-n-characters-in-filebeat/94544/4 "2017-08-15T21:35:18Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.