# It looks like you have instances that aren't connected to an Elasticsearch cluster

**URL:** <https://discuss.elastic.co/t/it-looks-like-you-have-instances-that-arent-connected-to-an-elasticsearch-cluster/323057>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [January 12, 2023, 7:59pm UTC](https://discuss.elastic.co/t/it-looks-like-you-have-instances-that-arent-connected-to-an-elasticsearch-cluster/323057 "2023-01-12T19:59:07Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [January 12, 2023, 7:59pm UTC](https://discuss.elastic.co/t/it-looks-like-you-have-instances-that-arent-connected-to-an-elasticsearch-cluster/323057/1 "2023-01-12T19:59:07Z")

</div>

Hello World!

 ![Screenshot 2023-01-12 at 1.55.06 PM](https://us1.discourse-cdn.com/elastic/original/3X/1/0/10dd1952801eeab1a55b0b1bd7330d77c9241585.png)

per the above screenshot, it appears like there are 2 (two) clusters, in reality there is only 1 (one)

the "standalone cluster" is using a separate set of _metricbeat_ vs the "elasticsearch" cluster, and what's even more odd is that some of the instances from "standalone cluster" metricbeat made into both clusters, even though there is no difference in between each of those metricbeat configurations..

Please advise!

---

<div class="post-metadata">

**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\
**Post date:** [January 13, 2023, 7:18am UTC](https://discuss.elastic.co/t/it-looks-like-you-have-instances-that-arent-connected-to-an-elasticsearch-cluster/323057/2 "2023-01-13T07:18:03Z")

</div>

Hi,

Have you already tried setting [monitoring.cluster\_uuid](https://www.elastic.co/guide/en/beats/metricbeat/8.6/configuration-monitor.html#_monitoring_cluster_uuid) in the Beats config?

Best regards  
Wolfram

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [January 14, 2023, 3:35pm UTC](https://discuss.elastic.co/t/it-looks-like-you-have-instances-that-arent-connected-to-an-elasticsearch-cluster/323057/3 "2023-01-14T15:35:37Z")

</div>

i did try setting up `monitoring.cluster_uuid`, unfortunately still getting same behavior (2 clusters: 1st actual elasticsearch cluster and the 2nd is "standalone cluster")

---

<div class="post-metadata">

**Author:** ![Ayush\_Mathur](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ayush_mathur/32/77134_2.png) [@Ayush\_Mathur](https://discuss.elastic.co/u/Ayush_Mathur)\
**Post date:** [January 23, 2023, 2:53pm UTC](https://discuss.elastic.co/t/it-looks-like-you-have-instances-that-arent-connected-to-an-elasticsearch-cluster/323057/4 "2023-01-23T14:53:59Z")

</div>

The monitoring data is stored in .es-monitoring index (not sure about datastream name for it), you after configuring UUID, you need to wait till the time last monitoring index containing both cluster information is archived and deleted.

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [January 24, 2023, 3:11am UTC](https://discuss.elastic.co/t/it-looks-like-you-have-instances-that-arent-connected-to-an-elasticsearch-cluster/323057/5 "2023-01-24T03:11:26Z")

</div>

> GET /\_cat/indices/.es-monitoring

```auto
{
  "error" : {
    "root_cause" : [
      {
        "type" : "index_not_found_exception",
        "reason" : "no such index [.es-monitoring]",
        "index_uuid" : "_na_",
        "resource.type" : "index_or_alias",
        "resource.id" : ".es-monitoring",
        "index" : ".es-monitoring"
      }
    ],
    "type" : "index_not_found_exception",
    "reason" : "no such index [.es-monitoring]",
    "index_uuid" : "_na_",
    "resource.type" : "index_or_alias",
    "resource.id" : ".es-monitoring",
    "index" : ".es-monitoring"
  },
  "status" : 404
}

```

* * *

yet

> GET /\_cat/indices/.monitoring-\*

there are bunch of indices, which i have deleted in the past to clear everything that have been stored previously, however that did not do the trick as i still get prompted to select cluster every time i go into monitoring app in kibana.

i even verified that cluster uuid exists in the actual event and there is no other value other then my cluster\_uuid..

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [January 24, 2023, 3:17am UTC](https://discuss.elastic.co/t/it-looks-like-you-have-instances-that-arent-connected-to-an-elasticsearch-cluster/323057/6 "2023-01-24T03:17:35Z")

</div>

possibly also worth to note this as well:

not all of logstash instances and logstash pipelines that made into `monitoring.cluster_uuid` specified cluster, made into "standard cluster". I find that odd, as all metricbeat instances are running exactly same configuration..

---

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [January 25, 2023, 5:33pm UTC](https://discuss.elastic.co/t/it-looks-like-you-have-instances-that-arent-connected-to-an-elasticsearch-cluster/323057/7 "2023-01-25T17:33:43Z")

</div>

I had this for years, across various versions, never got it fixed. Since everything shows in the proper cluster, mine couldn't have been missing UUID's. I just ignored it....

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [January 26, 2023, 3:34am UTC](https://discuss.elastic.co/t/it-looks-like-you-have-instances-that-arent-connected-to-an-elasticsearch-cluster/323057/8 "2023-01-26T03:34:15Z")

</div>

i guess i could ignore it but ...

... call me 🤪 but it's one extra click for moi 😉 and it's an old 🪲 for elastic to squeeze 😤 and _especially_ now it's been there for years, across various of versions)

---

<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:** [February 23, 2023, 3:34am UTC](https://discuss.elastic.co/t/it-looks-like-you-have-instances-that-arent-connected-to-an-elasticsearch-cluster/323057/9 "2023-02-23T03:34:34Z")

</div>

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