# Redundancy in logstash for syslog devices

**URL:** <https://discuss.elastic.co/t/redundancy-in-logstash-for-syslog-devices/261557>\
**Category:** Logstash\
**Created:** [January 19, 2021, 2:32pm UTC](https://discuss.elastic.co/t/redundancy-in-logstash-for-syslog-devices/261557 "2021-01-19T14:32:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Atul\_Chadha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atul_chadha/32/75469_2.png) [@Atul\_Chadha](https://discuss.elastic.co/u/Atul_Chadha)\
**Post date:** [January 19, 2021, 2:32pm UTC](https://discuss.elastic.co/t/redundancy-in-logstash-for-syslog-devices/261557/1 "2021-01-19T14:32:10Z")

</div>

We are in process of upgrading our ELK stack to 7.6 and i need suggestions on configuration for network devices ( Big IP LTM ) for example.

The current config has one logstash IP as syslog server , in an event of failure the logs dont reach the Elasticsearch servers

We have tried adding second log-stash as secondary server for syslog however this seems to generate duplicate entries on kibana

Is this a known behavior ? How we can achieve redundancy using two log-stash servers for syslog devices.

Filebeat is working fine.

---

<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:** [February 16, 2021, 2:32pm UTC](https://discuss.elastic.co/t/redundancy-in-logstash-for-syslog-devices/261557/2 "2021-02-16T14:32:12Z")

</div>

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