# Multiple syslog input from different Device to Logstash

**URL:** <https://discuss.elastic.co/t/multiple-syslog-input-from-different-device-to-logstash/188672>\
**Category:** Logstash\
**Created:** [July 3, 2019, 9:43am UTC](https://discuss.elastic.co/t/multiple-syslog-input-from-different-device-to-logstash/188672 "2019-07-03T09:43:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![IGSLXW](https://avatars.discourse-cdn.com/v4/letter/i/eada6e/32.png) [@IGSLXW](https://discuss.elastic.co/u/IGSLXW)\
**Post date:** [July 3, 2019, 9:43am UTC](https://discuss.elastic.co/t/multiple-syslog-input-from-different-device-to-logstash/188672/1 "2019-07-03T09:43:36Z")

</div>

We are having a logstash receiving syslog from multiple sources/hosts.  
Changing the syslog remote port from 514 to other is not our option.  
Is there any practice to separate / route the log from syslog to different pipeline?

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [July 3, 2019, 1:21pm UTC](https://discuss.elastic.co/t/multiple-syslog-input-from-different-device-to-logstash/188672/2 "2019-07-03T13:21:47Z")

</div>

If you want to route all of the events from the syslog input to a different pipeline you can do it by adding a [tag](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-syslog.html#plugins-inputs-syslog-tags) and a [distributor pattern](https://www.elastic.co/guide/en/logstash/current/pipeline-to-pipeline.html#distributor-pattern) with pipeline-to-pipeline communication.

---

<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:** [July 31, 2019, 1:21pm UTC](https://discuss.elastic.co/t/multiple-syslog-input-from-different-device-to-logstash/188672/3 "2019-07-31T13:21:50Z")

</div>

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