# Graylog showing \\n instead of multiline

**URL:** <https://community.graylog.org/t/graylog-showing-n-instead-of-multiline/10534>\
**Category:** Graylog Central (peer support)\
**Created:** [May 23, 2019, 8:09am UTC](https://community.graylog.org/t/graylog-showing-n-instead-of-multiline/10534 "2019-05-23T08:09:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![aseques](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/aseques/32/4472_2.png) [@aseques](https://community.graylog.org/u/aseques)\
**Post date:** [May 23, 2019, 8:09am UTC](https://community.graylog.org/t/graylog-showing-n-instead-of-multiline/10534/1 "2019-05-23T08:09:12Z")

</div>

I am using rsyslog to forward logs generated in tomcat (catalina.out), I configured rsyslog to use the syslog protocol 23 so I can have priority and ms in graylog.  
I am currently simulating the log sending with:  
`echo -e "`date ‘+%d-%b-%Y %H:%M:%S.%3N’`TEST\nRESULT" >> /var/log/tomcat8/catalina.out`  
The logs are being forwarded to graylog as expected but on the msg field in graylog the newlines are shown as \n instead of a proper newline.  
Where should I fix this so the newlines would be shown properly?

![Screenshot_20190523_100753](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/2X/f/fe1374b589759f9e0a2629463493db483ac0d4c6.png)

---

<div class="post-metadata">

**Author:** ![aseques](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/aseques/32/4472_2.png) [@aseques](https://community.graylog.org/u/aseques)\
**Post date:** [May 27, 2019, 8:34am UTC](https://community.graylog.org/t/graylog-showing-n-instead-of-multiline/10534/2 "2019-05-27T08:34:22Z")

</div>

Anyone? I have been looking through the documentation and I can’t find anything related to this, it must be something I am doing wrong but I can’t figure the cause.

---

<div class="post-metadata">

**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\
**Post date:** [May 27, 2019, 10:17am UTC](https://community.graylog.org/t/graylog-showing-n-instead-of-multiline/10534/3 "2019-05-27T10:17:39Z")

</div>

Graylog does see the incoming messages only as string and does not do any kind of interpretation on that.

You would need to open a feature request over in Github if you like to see this ability in Graylog.

> **[Graylog2/graylog2-server](https://github.com/Graylog2/graylog2-server/issues)**
>
> Free and open source log management. Contribute to Graylog2/graylog2-server development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![aseques](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/aseques/32/4472_2.png) [@aseques](https://community.graylog.org/u/aseques)\
**Post date:** [May 27, 2019, 10:55am UTC](https://community.graylog.org/t/graylog-showing-n-instead-of-multiline/10534/4 "2019-05-27T10:55:36Z")

</div>

Done, I opened the issue here, thanks

> <https://github.com/Graylog2/graylog2-server/issues/5971>

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [June 10, 2019, 10:55am UTC](https://community.graylog.org/t/graylog-showing-n-instead-of-multiline/10534/5 "2019-06-10T10:55:36Z")

</div>

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