# Consolidate filebeats

**URL:** <https://discuss.elastic.co/t/consolidate-filebeats/349653>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [December 19, 2023, 1:55pm UTC](https://discuss.elastic.co/t/consolidate-filebeats/349653 "2023-12-19T13:55:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vee/32/55759_2.png) [@vee](https://discuss.elastic.co/u/vee)\
**Post date:** [December 19, 2023, 1:55pm UTC](https://discuss.elastic.co/t/consolidate-filebeats/349653/1 "2023-12-19T13:55:32Z")

</div>

Hi - we have a situation where different log files are being sent to diff logstash outputs and it's getting out of control with more than 7-8 instances running at the moment on a bunch of the key servers. I am trying to consolidate all these filebeat instances into one, possibly.

One idea was to have a master logstash which would look for a specific string in the source message, and then route to appropriate downstream logstash pipelines. Instead, is there a way to send the output to multiple from filebeat process itself - say, if message contains "abc" send to abc logstash pipeline etc. I did see that it can be done through ingest pipelines - but that would be to skip logstash and we don't want to excessive load on ingest nodes - given their current sizing.

How are others dealing with this kind of situation? Any ideas can be helpful in us making the right decision.

Thanks,  
Veeresh

---

<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:** [January 16, 2024, 3:55pm UTC](https://discuss.elastic.co/t/consolidate-filebeats/349653/2 "2024-01-16T15:55:35Z")

</div>

Closed on January 16, 2024, 3:55pm UTC

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