---
title: Cluster Name
description: Describes what AutoOps detects and surfaces with the Cluster Name insight: The cluster still uses a default Elasticsearch cluster name.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/cluster_name
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# Cluster Name
The cluster still uses a default Elasticsearch cluster name. Nodes on the same network with the same name can join the wrong cluster, which can mix environments and data.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch).
</note>


## Insight details


| Field     | Value         |
|-----------|---------------|
| Component | Elasticsearch |
| Severity  | Low           |
| Scope     | Cluster       |
| Domains   | configuration |


## Example: What you might see in AutoOps

The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.

### The cluster name is set to default: 'prod-logs-cluster'


#### What was detected

_No description available._

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="Change the cluster name">
  **Condition**: Always shown for this insight.The cluster still uses the default name. Set a unique `cluster.name` so nodes and monitoring clearly identify this cluster.
</dropdown>


#### Background and impact

Impact: Default names can lead to nodes joining the wrong clusters.
An Elasticsearch node will try to form a cluster with other nodes in its network that have the same cluster name that is set in its elasticsearch.yml configuration.
If you leave the default name for your cluster you run the risk of a development node inadvertently joining the production cluster in the same network in the future.