# \[SOLVED\] How to manage HUGE log messages sent to ELK stack over-the-wire?

**URL:** <https://discuss.elastic.co/t/solved-how-to-manage-huge-log-messages-sent-to-elk-stack-over-the-wire/78054>\
**Category:** Logstash\
**Created:** [March 9, 2017, 9:45pm UTC](https://discuss.elastic.co/t/solved-how-to-manage-huge-log-messages-sent-to-elk-stack-over-the-wire/78054 "2017-03-09T21:45:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ZillaG](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zillag/32/10505_2.png) [@ZillaG](https://discuss.elastic.co/u/ZillaG)\
**Post date:** [March 9, 2017, 9:45pm UTC](https://discuss.elastic.co/t/solved-how-to-manage-huge-log-messages-sent-to-elk-stack-over-the-wire/78054/1 "2017-03-09T21:45:29Z")

</div>

I've been using ELK for centralized logging service, and rsyslog as my shipper. Rsyslog wraps the log events in a JSON format.

However, some of our application logs are HUGE, e.g., stack traces, and when Logstash receives them, the log is truncated, resulting in \_jsonparsefailure. I've tried sending the logs either via UDP/UDP6 and TCP/TCP6 to no avail.

How have some of you manage to solve this? I'm sure I'm not the only one in this predicament.

Thanks!

---

<div class="post-metadata">

**Author:** ![ZillaG](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zillag/32/10505_2.png) [@ZillaG](https://discuss.elastic.co/u/ZillaG)\
**Post date:** [March 10, 2017, 4:44pm UTC](https://discuss.elastic.co/t/solved-how-to-manage-huge-log-messages-sent-to-elk-stack-over-the-wire/78054/2 "2017-03-10T16:44:38Z")

</div>

For rsysog users, see [How to ship JSON logs via Rsyslog](https://techpunch.co.uk/development/how-to-shop-json-logs-via-rsyslog), especially the $MaxMessageSize setting. This along with the buffer\_size setting solved my issues where large log events were being truncated.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [March 11, 2017, 6:07pm UTC](https://discuss.elastic.co/t/solved-how-to-manage-huge-log-messages-sent-to-elk-stack-over-the-wire/78054/3 "2017-03-11T18:07:37Z")

</div>

Thanks for sharing this solution!

---

<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:** [April 8, 2017, 6:07pm UTC](https://discuss.elastic.co/t/solved-how-to-manage-huge-log-messages-sent-to-elk-stack-over-the-wire/78054/4 "2017-04-08T18:07:52Z")

</div>

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