# Logstash syslog TCP output breaking to parts
**URL:** https://discuss.elastic.co/t/logstash-syslog-tcp-output-breaking-to-parts/110551
**Category:** Logstash
**Created:** [December 6, 2017, 5:37pm UTC](https://discuss.elastic.co/t/logstash-syslog-tcp-output-breaking-to-parts/110551 "2017-12-06T17:37:11Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@dorr](https://discuss.elastic.co/u/dorr)
#### Post date: [December 6, 2017, 5:37pm UTC](https://discuss.elastic.co/t/logstash-syslog-tcp-output-breaking-to-parts/110551/1 "2017-12-06T17:37:12Z")
Hi, question I got from a customer regarding Logstash 2.3.4 we use there:
- I've noticed that the logs are sent in multiple syslog message. 1 application log item = X tcp syslog request. Is it possible to make 1 application log item = 1 tcp syslog even if it is big ?
Thanks.
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [December 18, 2017, 7:14pm UTC](https://discuss.elastic.co/t/logstash-syslog-tcp-output-breaking-to-parts/110551/2 "2017-12-18T19:14:33Z")
It depends. Is there anything in the messages that indicate that they've been split up?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 15, 2018, 7:14pm UTC](https://discuss.elastic.co/t/logstash-syslog-tcp-output-breaking-to-parts/110551/3 "2018-01-15T19:14:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.