# Z names with an elastic index

**URL:** <https://discuss.elastic.co/t/z-names-with-an-elastic-index/289066>\
**Category:** Elasticsearch\
**Created:** [November 12, 2021, 12:21pm UTC](https://discuss.elastic.co/t/z-names-with-an-elastic-index/289066 "2021-11-12T12:21:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tractor\_boy](https://avatars.discourse-cdn.com/v4/letter/t/278dde/32.png) [@tractor\_boy](https://discuss.elastic.co/u/tractor_boy)\
**Post date:** [November 12, 2021, 12:21pm UTC](https://discuss.elastic.co/t/z-names-with-an-elastic-index/289066/1 "2021-11-12T12:21:39Z")

</div>

I support an environment similar to AWS where the server names are of limited(/no) value in their raw form, so we have aliased them such that they are meaningful. If the server were rebuilt the zname would change, but the alias not.

I require all data captured in elastic to reference the alias and not the zname.

What do I need to do to make that happen?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 14, 2021, 9:15pm UTC](https://discuss.elastic.co/t/z-names-with-an-elastic-index/289066/2 "2021-11-14T21:15:13Z")

</div>

You'd need to make your ingest process use it.

---

<div class="post-metadata">

**Author:** ![tractor\_boy](https://avatars.discourse-cdn.com/v4/letter/t/278dde/32.png) [@tractor\_boy](https://discuss.elastic.co/u/tractor_boy)\
**Post date:** [November 15, 2021, 8:23am UTC](https://discuss.elastic.co/t/z-names-with-an-elastic-index/289066/3 "2021-11-15T08:23:18Z")

</div>

Sorry, are you able to explain what you mean by "make your ingest process use it"? Thanks

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 15, 2021, 10:10pm UTC](https://discuss.elastic.co/t/z-names-with-an-elastic-index/289066/4 "2021-11-15T22:10:20Z")

</div>

You'd have to create something to do the rename as you index the data into Elasticsearch.  
So an ingest pipeline, Logstash, something custom.

---

<div class="post-metadata">

**Author:** ![tractor\_boy](https://avatars.discourse-cdn.com/v4/letter/t/278dde/32.png) [@tractor\_boy](https://discuss.elastic.co/u/tractor_boy)\
**Post date:** [November 16, 2021, 10:56am UTC](https://discuss.elastic.co/t/z-names-with-an-elastic-index/289066/5 "2021-11-16T10:56:55Z")

</div>

We may have found a way, in that we have defined a host friendly name in the metric beats config, which seems to be appended to all the indexes, so we just need to make sure that that variable is visualised when building visualisations.

This is hopefully simpler than building out some code to rename content on the fly.

---

<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:** [December 14, 2021, 10:57am UTC](https://discuss.elastic.co/t/z-names-with-an-elastic-index/289066/6 "2021-12-14T10:57:56Z")

</div>

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