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.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Low |
| Scope | Cluster |
| Domains | configuration |
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.
cluster.name is still the default value (prod-logs-cluster).
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
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.
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.