# Multiple Filebeat instances with separate configuration files to different Logstash containers
**URL:** https://discuss.elastic.co/t/multiple-filebeat-instances-with-separate-configuration-files-to-different-logstash-containers/195984
**Category:** Beats
**Tags:** filebeat
**Created:** [August 20, 2019, 7:06pm UTC](https://discuss.elastic.co/t/multiple-filebeat-instances-with-separate-configuration-files-to-different-logstash-containers/195984 "2019-08-20T19:06:47Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@kmiklas](https://discuss.elastic.co/u/kmiklas)
#### Post date: [August 20, 2019, 7:06pm UTC](https://discuss.elastic.co/t/multiple-filebeat-instances-with-separate-configuration-files-to-different-logstash-containers/195984/1 "2019-08-20T19:06:47Z")
Is it possible to run multiple instances of Filebeat with different filebeat.yml config files?
I need to send log lines to different servers running Logstash.
Thx, Keith :^)
---
### Author:  [@MarianaD](https://discuss.elastic.co/u/MarianaD)
#### Post date: [August 21, 2019, 7:36am UTC](https://discuss.elastic.co/t/multiple-filebeat-instances-with-separate-configuration-files-to-different-logstash-containers/195984/2 "2019-08-21T07:36:13Z")
hi @kmiklas, can you confirm the scenario here, do you want to send same data to multiple logstash server simultaneously or are you talking about a load balance scenario? If the latter, have a look here [https://www.elastic.co/guide/en/beats/filebeat/current/load-balancing.html](https://www.elastic.co/guide/en/beats/filebeat/current/load-balancing.html).
Else, the first option is not supported, more on this here: [Support multiple outputs of the same type (like two independent Logstash clusters) · Issue #1035 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/1035).
Alternatives to this scenario were previously advised in a different discuss ticket:
> 1. run multiple filebeat instance, each with different registry file, to have separate state for each cluster to send traffic too.
> 2. have filebeat push to kafka + use 2 LS instances/clusters (1LS per required output) with different consumer-groups. The consumer groups uncouple the systems
> 3. Use redis publish-subscribe (type: channels) to push events. Drawback: if LS is down, one ES cluster might not get any data (potential data loss).
> 4. implement some kind of replication: Still couple the systems, but have filebeat send to LS and LS push to local ES + queue(file, S3, redis, kafka, whatever). Have second LS forward the logs in queue to second ES instance.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [September 18, 2019, 7:36am UTC](https://discuss.elastic.co/t/multiple-filebeat-instances-with-separate-configuration-files-to-different-logstash-containers/195984/3 "2019-09-18T07:36:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.