# Stack monitoring when using Pipeline to Pipeline communication

**URL:** <https://discuss.elastic.co/t/stack-monitoring-when-using-pipeline-to-pipeline-communication/225861>\
**Category:** Logstash\
**Tags:** elastic-stack-monitoring\
**Created:** [March 31, 2020, 12:37pm UTC](https://discuss.elastic.co/t/stack-monitoring-when-using-pipeline-to-pipeline-communication/225861 "2020-03-31T12:37:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![niklaskurvinen](https://avatars.discourse-cdn.com/v4/letter/n/cdc98d/32.png) [@niklaskurvinen](https://discuss.elastic.co/u/niklaskurvinen)\
**Post date:** [March 31, 2020, 12:37pm UTC](https://discuss.elastic.co/t/stack-monitoring-when-using-pipeline-to-pipeline-communication/225861/1 "2020-03-31T12:37:01Z")

</div>

Hi all!

Stack version: 7.6.0

Using the new remote monitoring (monitoring the elastic stack using metricbeat) I bumped into something that I can't find a solution for.

In the Stack Monitoring view in Kibana I now, after configuring Pipeline to Pipeline communication, always get two clusters: My actual cluster and the "Standalone Cluster".

In the Standalone Cluster I can see my single logstash node (that is using Pipeline to Pipeline communication) together with one (1) pipeline; the pipeline that is using the pipeline output. Note that the same logstash node is also included in my actual cluster, but here with only the other pipeline, the one using the elasticsearch output plugin.

My Pipelines:

**input-beats.conf** - Standalone Cluster

```auto
    input {
      beats {
        port => 5044
      }
    }

    output {
      pipeline {
        send_to => ["output-elasticsearch"]
      }
    }

```

**output-elasticsearch.conf** - Correct cluster

```auto
    input {
      pipeline {
        address => "output-elasticsearch"
      }
    }

    output {
      elasticsearch{
        # my output config
      }
    }

```

So, the data is arriving and all is well. But why isn't the first pipeline recognized as part of my actual cluster?  
I'm guessing that the elasticsearch output plugin finds the cluster.uuid automatically and uses that to identify with the cluster, but isn't there any way for my input pipeline to do this as well? Or at least a way to tell it which cluster it belongs to in the configuration?

Can't seem to find an answer to this after some heavy reading on documentation and google.

---

<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:** [April 1, 2020, 2:00pm UTC](https://discuss.elastic.co/t/stack-monitoring-when-using-pipeline-to-pipeline-communication/225861/2 "2020-04-01T14:00:10Z")

</div>

Hi @niklaskurvinen,

Thanks for raising this issue!

I managed to successfully reproduce this locally and there is a work around coming: [https://github.com/elastic/logstash/pull/11106](https://github.com/elastic/logstash/pull/11106)

With this PR, you'll be able to add a new setting `monitoring.cluster_uuid` which will ensure all monitoring data is stored under that cluster which will mean you won't see the Standalone Cluster anymore.

Lemme know if that helps

---

<div class="post-metadata">

**Author:** ![niklaskurvinen](https://avatars.discourse-cdn.com/v4/letter/n/cdc98d/32.png) [@niklaskurvinen](https://discuss.elastic.co/u/niklaskurvinen)\
**Post date:** [April 2, 2020, 1:13pm UTC](https://discuss.elastic.co/t/stack-monitoring-when-using-pipeline-to-pipeline-communication/225861/3 "2020-04-02T13:13:21Z")

</div>

Thanks @chrisronline!

Figured that there would be a PR somewhere, that's perfect!

---

<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:** [April 30, 2020, 1:13pm UTC](https://discuss.elastic.co/t/stack-monitoring-when-using-pipeline-to-pipeline-communication/225861/4 "2020-04-30T13:13:21Z")

</div>

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