﻿---
title: Default cluster name
description: Describes what AutoOps detects and surfaces with the Default 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/default_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
---

# Default 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 and mix environments or 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

`cluster.name` is still the default value (`prod-logs-cluster`).

#### 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

An Elasticsearch node forms a cluster with other reachable nodes that share the same `cluster.name` from `elasticsearch.yml`.
Leaving the default name increases the chance that a development or test node joins a production cluster on the same network. That can mix data, settings, and traffic across environments.
Use a unique name per environment before nodes that should stay separate can discover each other.