# Persistent node names
**URL:** https://discuss.elastic.co/t/persistent-node-names/173153
**Category:** Elastic Cloud Enterprise (ECE)
**Created:** [March 20, 2019, 1:37pm UTC](https://discuss.elastic.co/t/persistent-node-names/173153 "2019-03-20T13:37:05Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@osykora](https://discuss.elastic.co/u/osykora)
#### Post date: [March 20, 2019, 1:37pm UTC](https://discuss.elastic.co/t/persistent-node-names/173153/1 "2019-03-20T13:37:05Z")
Hi,
a node name looks like "instance-0000000001" and is incremented on every cluster update. This is fine until one takes a look into Kibana Monitoring tab and finds out that a new node got created there as well and that the node's historical data can be found under the old node's name only.
Isn't there a way to instruct ECE not to rename nodes on update or to use an alias instead so that the Monitoring tab shows full nodes history?
---
### Author:  [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)
#### Post date: [March 20, 2019, 1:57pm UTC](https://discuss.elastic.co/t/persistent-node-names/173153/2 "2019-03-20T13:57:49Z")
Thanks for reporting this. We don't currently have a great story here I agree.
Note that as of 2.1 we make it easier to do rolling upgrades which preserve the instance id (and at some point that will become the default)
I'm opening an internal issue to discuss what we do about this
Alex
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 3, 2019, 1:57pm UTC](https://discuss.elastic.co/t/persistent-node-names/173153/3 "2019-04-03T13:57:50Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.