# Display Name for Index Patterns

**URL:** <https://discuss.elastic.co/t/display-name-for-index-patterns/302357>\
**Category:** Kibana\
**Created:** [April 13, 2022, 3:30pm UTC](https://discuss.elastic.co/t/display-name-for-index-patterns/302357 "2022-04-13T15:30:55Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tim\_Mobley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tim_mobley/32/94741_2.png) [@Tim\_Mobley](https://discuss.elastic.co/u/Tim_Mobley)\
**Post date:** [April 13, 2022, 3:30pm UTC](https://discuss.elastic.co/t/display-name-for-index-patterns/302357/1 "2022-04-13T15:30:55Z")

</div>

I was wondering if it is possible to use a different, more intuitive/human-readable, display name for index patterns in Discover rather than the actual pattern? My reason is that some index patterns are ugly and I'd it to be easier for my end users to find the data they are looking for.

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [April 13, 2022, 3:44pm UTC](https://discuss.elastic.co/t/display-name-for-index-patterns/302357/2 "2022-04-13T15:44:14Z")

</div>

@Tim_Mobley ,

What about using data streams ?

> **[Data streams | Elasticsearch Guide \[8.1\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams.html)**

With customised names, changing mostly the dataset and namespace.

> **[Elasticsearch output plugin | Logstash Reference \[8.1\] | Elastic](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html#plugins-outputs-elasticsearch-data-streams)**

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [April 13, 2022, 4:20pm UTC](https://discuss.elastic.co/t/display-name-for-index-patterns/302357/3 "2022-04-13T16:20:14Z")

</div>

@Tim_Mobley Have a few examples I use myself

---

<div class="post-metadata">

**Author:** ![matw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matw/32/13913_2.png) [@matw](https://discuss.elastic.co/u/matw)\
**Post date:** [April 13, 2022, 4:26pm UTC](https://discuss.elastic.co/t/display-name-for-index-patterns/302357/4 "2022-04-13T16:26:29Z")

</div>

Hi @Tim_Mobley  
Have a look at this PR which is in review in Kibana:

> <https://github.com/elastic/kibana/pull/124191>
>
> \## Summary
> 
> - Ability to edit data view. Closes #119175
> - Ability to set h…uman readable title of data view #117143
> 
> 
> \### Images
> 
> 
> !\[Screenshot\_20220201\_003440\](https://user-images.githubusercontent.com/5311338/151891056-e037eb87-5288-4c93-a1ef-9dca8cc6679a.png)
> !\[Screenshot 2022-02-23 000546\](https://user-images.githubusercontent.com/5311338/155234607-9447fe2d-7331-4be0-a693-86eabcdb6e07.png)
> !\[Screenshot\_20220201\_003509\](https://user-images.githubusercontent.com/5311338/151891058-2a87d911-f395-445a-ab88-e710b9664452.png)
> !\[Screenshot\_20220201\_003626\](https://user-images.githubusercontent.com/5311338/151891061-cb8a0be7-16d3-4de3-9fa9-a6c9b10e0288.png)
> !\[Screenshot\_20220201\_003534\](https://user-images.githubusercontent.com/5311338/151891060-bbc2f3f1-7563-45e8-bb1e-09bf857e6f77.png)
> !\[Screenshot\_20220201\_003649\](https://user-images.githubusercontent.com/5311338/151891062-0943138c-e023-4016-bc93-6207d31f893c.png)
> 
> 
> 
> 
> \### Checklist
> 
> Delete any items that are not applicable to this PR.
> 
> \- \[x\] Any text added follows \[EUI's writing guidelines\](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes \[i18n support\](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
> \- \[x\] \[Documentation\](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials
> \- \[x\] \[Unit or functional tests\](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
> \- \[x\] Any UI touched in this PR is usable by keyboard only (learn more about \[keyboard accessibility\](https://webaim.org/techniques/keyboard/))
> \- \[x\] This renders correctly on smaller devices using a responsive layout. (You can test this \[in your browser\](https://www.browserstack.com/guide/responsive-testing-on-local-server))
> \- \[x\] This was checked for \[cross-browser compatibility\](https://www.elastic.co/support/matrix#matrix\_browsers)

Think that this is what you're looking for?

Best,  
Matthias

---

<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:** [May 11, 2022, 4:26pm UTC](https://discuss.elastic.co/t/display-name-for-index-patterns/302357/5 "2022-05-11T16:26:41Z")

</div>

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