# Logstash monitoring: pipeline identification

**URL:** https://discuss.elastic.co/t/logstash-monitoring-pipeline-identification/207300
**Category:** Kibana
**Created:** [November 11, 2019, 8:21am UTC](https://discuss.elastic.co/t/logstash-monitoring-pipeline-identification/207300 "2019-11-11T08:21:39Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![asp](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@asp](https://discuss.elastic.co/u/asp)
#### Post date: [November 11, 2019, 8:21am UTC](https://discuss.elastic.co/t/logstash-monitoring-pipeline-identification/207300/1 "2019-11-11T08:21:39Z")

</div>

Hi,

I am running multiple logstash instances in kubernetes. In elastic's monitoring I see same pipeline once per node:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/c/2c81969b935cbc0ab3de50d14ecf24c0ca442264.png)  
My idea is to see in the overview panel all identical pipelines of all nodes to be aggregated. Meaning In overview I see only one blob pipeline, if the configuration of this pipeline is identical. If I filter first for a specific node and then go to pipeline tab I see the pipeline stats of the selected node.

What do I have to do that the monitoring is able to recognize that the pipelines are identical?  
Do I have to add any ids or versions somewhere inside the pipeline configuration?

Thanks, Andreas

---

<div class="post-metadata">

### Author: ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [November 18, 2019, 9:48pm UTC](https://discuss.elastic.co/t/logstash-monitoring-pipeline-identification/207300/2 "2019-11-18T21:48:55Z")

</div>

Hi @asp,

What version of the stack are you using?

---

<div class="post-metadata">

### Author: ![asp](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@asp](https://discuss.elastic.co/u/asp)
#### Post date: [November 19, 2019, 7:39am UTC](https://discuss.elastic.co/t/logstash-monitoring-pipeline-identification/207300/3 "2019-11-19T07:39:54Z")

</div>

7.4.2

---

<div class="post-metadata">

### Author: ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [November 19, 2019, 6:59pm UTC](https://discuss.elastic.co/t/logstash-monitoring-pipeline-identification/207300/4 "2019-11-19T18:59:34Z")

</div>

You might be running into this issue here: [https://github.com/elastic/kibana/issues/49462](https://github.com/elastic/kibana/issues/49462)

---

<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: [December 17, 2019, 6:59pm UTC](https://discuss.elastic.co/t/logstash-monitoring-pipeline-identification/207300/5 "2019-12-17T18:59:49Z")

</div>

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