# Which version of logstash support for multiple which version of logstash can support multiple pipline?

**URL:** <https://discuss.elastic.co/t/which-version-of-logstash-support-for-multiple-which-version-of-logstash-can-support-multiple-pipline/118421>\
**Category:** Logstash\
**Created:** [February 5, 2018, 9:50am UTC](https://discuss.elastic.co/t/which-version-of-logstash-support-for-multiple-which-version-of-logstash-can-support-multiple-pipline/118421 "2018-02-05T09:50:23Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robin\_Guo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robin_guo/32/42297_2.png) [@Robin\_Guo](https://discuss.elastic.co/u/Robin_Guo)\
**Post date:** [February 5, 2018, 9:50am UTC](https://discuss.elastic.co/t/which-version-of-logstash-support-for-multiple-which-version-of-logstash-can-support-multiple-pipline/118421/1 "2018-02-05T09:50:23Z")

</div>

Hi ES team,

I wonder know , **which version of Logstash** can support multiple pipline within a group of logstash server by now?

Currently we used **few beats** on monitored side ,whatever **metricbeat/filebeat/heartbeat** or **the beat** we build by ourselves.

But we have to assign **a dedicated logstash cluster** for **a group of particular beat**.

My question is that can newer logstash support more multiple pipline instead of one beat corresponding to one logstash?

Thanks

* * *

for example:

#/etc/logstash/conf.d

- filebeat.conf

```auto
#logstash for filebeat
input {
  beats {
    port => 5044
  }
}
 
filter {
   mutate { add_field => { "[@metadata][index_prefix]" => "%{env}-%{dc}-%{os}-%{service}" } }
   mutate { remove_field => ["dc","env","os","service","type"] }

}

output {
  elasticsearch {
     hosts => ["estest01.tls.ad:9200","estest02.tls.ad:9200"]
     template_overwrite => false
     manage_template => false
     index => "%{[@metadata][index_prefix]}-%{+YYYY.MM.dd}"
     sniffing => false
     
   }
}

```

- heartbeat.conf

```auto
#logstash for heartbeat
input {
  beats {
    port => 5045
  }
}
 
filter {
   mutate { add_field => { "[@metadata][index_prefix]" => "%{env}-%{dc}-%{os}-%{service}" } }
   mutate { remove_field => ["dc","env","os","service","type"] }

}

output {
  elasticsearch {
     hosts => ["estest03.tls.ad:9200","estest04.tls.ad:9200"]
     template_overwrite => false
     manage_template => false
     index => "%{[@metadata][index_prefix]}-%{+YYYY.MM.dd}"
     sniffing => false
     
   }
}

```

- metricbeat.conf

```auto
#logstash for metricbeat
input {
  beats {
    port => 5046
  }
}
 
filter {
   mutate { add_field => { "[@metadata][index_prefix]" => "%{env}-%{dc}-%{os}-%{service}" } }
   mutate { remove_field => ["dc","env","os","service","type"] }

}

output {
  elasticsearch {
     hosts => ["estest05.tls.ad:9200","estest06.tls.ad:9200"]
     template_overwrite => false
     manage_template => false
     index => "%{[@metadata][index_prefix]}-%{+YYYY.MM.dd}"
     sniffing => false
     
   }
}

```

- tcpbeat.conf

```auto
#logstash for tcp
input {
  tcp {
    port => 5047
  }
}
 
filter {
   mutate { add_field => { "[@metadata][index_prefix]" => "%{env}-%{dc}-%{os}-%{service}" } }
   mutate { remove_field => ["dc","env","os","service","type"] }

}

output {
  elasticsearch {
     hosts => ["estest07.tls.ad:9200","estest08.tls.ad:9200"]
     template_overwrite => false
     manage_template => false
     index => "%{[@metadata][index_prefix]}-%{+YYYY.MM.dd}"
     sniffing => false
     
   }
}

```

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [February 5, 2018, 1:52pm UTC](https://discuss.elastic.co/t/which-version-of-logstash-support-for-multiple-which-version-of-logstash-can-support-multiple-pipline/118421/2 "2018-02-05T13:52:00Z")

</div>

Multi-pipeline support was added in Logstash 6.0.

> But we have to assign a dedicated logstash cluster for a group of particular beat.

Why do you think you have to do that?

---

<div class="post-metadata">

**Author:** ![Robin\_Guo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robin_guo/32/42297_2.png) [@Robin\_Guo](https://discuss.elastic.co/u/Robin_Guo)\
**Post date:** [February 6, 2018, 3:18am UTC](https://discuss.elastic.co/t/which-version-of-logstash-support-for-multiple-which-version-of-logstash-can-support-multiple-pipline/118421/3 "2018-02-06T03:18:43Z")

</div>

Because currently we used v5.5.2, It doesn't support multiple pipline yet.  
So we have to implement multiple pipline conf with a few groups of logstash clusters. which each pipline conf with a group of logstash cluster.

We distinguish between different kind of beats through the port instead of field type/flag by far. we use same port for same beat service.

is that clear?

Do you have any good suggestions for that?

Thanks in advance

Thanks

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [February 6, 2018, 6:40am UTC](https://discuss.elastic.co/t/which-version-of-logstash-support-for-multiple-which-version-of-logstash-can-support-multiple-pipline/118421/4 "2018-02-06T06:40:18Z")

</div>

> We distinguish between different kind of beats through the port instead of field type/flag by far. we use same port for same beat service.

I think that's an unnecessary complication.

> Do you have any good suggestions for that?

If you insist on using different ports and want to isolate different kinds of events then using the multi-pipeline feature is a good idea, but I wouldn't do it myself.

---

<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:** [March 6, 2018, 6:40am UTC](https://discuss.elastic.co/t/which-version-of-logstash-support-for-multiple-which-version-of-logstash-can-support-multiple-pipline/118421/5 "2018-03-06T06:40:24Z")

</div>

Closed on March 6, 2018, 6:40am UTC

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