# Logstash best practice

**URL:** <https://discuss.elastic.co/t/logstash-best-practice/85425>\
**Category:** Logstash\
**Created:** [May 11, 2017, 2:36pm UTC](https://discuss.elastic.co/t/logstash-best-practice/85425 "2017-05-11T14:36:17Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![talial](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@talial](https://discuss.elastic.co/u/talial)\
**Post date:** [May 15, 2017, 7:06am UTC](https://discuss.elastic.co/t/logstash-best-practice/85425/7 "2017-05-15T07:06:24Z")

</div>

> Sure, but it's not clear to me how you'll utilize both servers (hence my question about load balancing). As opposed to Elasticsearch, Logstash instance don't form clusters.

--\> the load balancer is F5 with TCP

If I understand correctly F5 will do the balancing to the 2 clients servers and so I will have highly availability with the logstash also?  
Also read this form:

> [@How to make Logstash highly available](https://discuss.elastic.co/t/how-to-make-logstash-highly-available/29926/4):
>
> @vikas_gopal @magnusbaeck Check out this discussion as well:

and found that F5 is good for this configuration, Is it correct?

---

_[View the full topic](https://discuss.elastic.co/t/logstash-best-practice/85425)._
