# Logstash Pipeline Set-up and Architecture

**URL:** <https://discuss.elastic.co/t/logstash-pipeline-set-up-and-architecture/172948>\
**Category:** Logstash\
**Created:** [March 19, 2019, 11:04am UTC](https://discuss.elastic.co/t/logstash-pipeline-set-up-and-architecture/172948 "2019-03-19T11:04:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![robincher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robincher/32/41282_2.png) [@robincher](https://discuss.elastic.co/u/robincher)\
**Post date:** [March 19, 2019, 11:04am UTC](https://discuss.elastic.co/t/logstash-pipeline-set-up-and-architecture/172948/1 "2019-03-19T11:04:40Z")

</div>

Hi all,

Currently i have one cluster of LogStash nodes ,and fronted by a load-balancer with a fully qualified domain name. For the logstash configuration, i allows all beats to pipe their logs into a single port (by default its 5044)

My question is, is there any good practices on how logstash should be architect? Especially when it start to scale, having a single logstash might not be the best way to go.

Some options i was pondering

1. Have multiple logstash cluster handling different beats/system inputs
2. Have multiple ports within Logstash to handle different beats/system inputs

Advice/comments are appreciated! Thanks!

---

<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 16, 2019, 11:05am UTC](https://discuss.elastic.co/t/logstash-pipeline-set-up-and-architecture/172948/2 "2019-04-16T11:05:13Z")

</div>

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