# Field available in Discover is not available in Visualizations

**URL:** <https://discuss.elastic.co/t/field-available-in-discover-is-not-available-in-visualizations/287987>\
**Category:** Kibana\
**Created:** [October 29, 2021, 9:56am UTC](https://discuss.elastic.co/t/field-available-in-discover-is-not-available-in-visualizations/287987 "2021-10-29T09:56:05Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![WimM](https://avatars.discourse-cdn.com/v4/letter/w/9fc348/32.png) [@WimM](https://discuss.elastic.co/u/WimM)\
**Post date:** [October 29, 2021, 9:56am UTC](https://discuss.elastic.co/t/field-available-in-discover-is-not-available-in-visualizations/287987/1 "2021-10-29T09:56:05Z")

</div>

Hi

We've setup ELK/Kibana for one of our applications and using the Discover "Top 5" feature we could quickly identify a specific issue:

![kibanadiscover](https://us1.discourse-cdn.com/elastic/original/3X/9/6/966648af7ae0435e514863160755605609b2d661.jpeg)

I wanted to get this exact same thing (top 5 of field "message") in a Visualization e.g. pie so I could add it to our dashboard but was a bit surprised that I couldn't find back that field in the Visualization.

Anybody any idea what could be the reason?

I did notice this field isn't flagged as aggregatable, could it be linked?

 ![kibana_agg](https://us1.discourse-cdn.com/elastic/original/3X/4/c/4c4f1ca15de8a18d46493cea7e3dbcdd7e30f203.jpeg)

Thx  
Wim

---

<div class="post-metadata">

**Author:** ![nate\_d](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nate_d/32/77076_2.png) [@nate\_d](https://discuss.elastic.co/u/nate_d)\
**Post date:** [October 29, 2021, 12:29pm UTC](https://discuss.elastic.co/t/field-available-in-discover-is-not-available-in-visualizations/287987/2 "2021-10-29T12:29:01Z")

</div>

You should have another field with the name `message.keyword` which is aggregateable.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/e/3e14eb0cadf81551a829593f70dc271f36b59330.png)

You can use message.keyword in you visualizations

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/1/31272def65f98c40f3f41fcf50cdfa49e0ae43d4.png)

---

<div class="post-metadata">

**Author:** ![WimM](https://avatars.discourse-cdn.com/v4/letter/w/9fc348/32.png) [@WimM](https://discuss.elastic.co/u/WimM)\
**Post date:** [October 29, 2021, 12:49pm UTC](https://discuss.elastic.co/t/field-available-in-discover-is-not-available-in-visualizations/287987/3 "2021-10-29T12:49:29Z")

</div>

Hi Nathan

thanks for your reply, however I don't have the message.keyword unfortunately

Is this something which needs to be configured?

Brgds  
Wim

---

<div class="post-metadata">

**Author:** ![WimM](https://avatars.discourse-cdn.com/v4/letter/w/9fc348/32.png) [@WimM](https://discuss.elastic.co/u/WimM)\
**Post date:** [November 8, 2021, 7:59am UTC](https://discuss.elastic.co/t/field-available-in-discover-is-not-available-in-visualizations/287987/4 "2021-11-08T07:59:06Z")

</div>

up... anybody able to help out or point me in the right direction?

thx!  
Wim

---

<div class="post-metadata">

**Author:** ![WimM](https://avatars.discourse-cdn.com/v4/letter/w/9fc348/32.png) [@WimM](https://discuss.elastic.co/u/WimM)\
**Post date:** [November 25, 2021, 12:43pm UTC](https://discuss.elastic.co/t/field-available-in-discover-is-not-available-in-visualizations/287987/5 "2021-11-25T12:43:30Z")

</div>

anyone?

---

<div class="post-metadata">

**Author:** ![ghudgins](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ghudgins/32/138532_2.png) [@ghudgins](https://discuss.elastic.co/u/ghudgins)\
**Post date:** [November 30, 2021, 1:20am UTC](https://discuss.elastic.co/t/field-available-in-discover-is-not-available-in-visualizations/287987/6 "2021-11-30T01:20:42Z")

</div>

if you are indexing the data Elasticsearch uses a dynamic mapping to assign the right field type based on the data it sees. It does not always map fields to be aggregatable in visualizations. You can make it use any mapping you want it to. Maybe give this a try by using an [Explicit mapping | Elasticsearch Guide [7.15] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/explicit-mapping.html)

try mapping it as a `keyword` field

---

<div class="post-metadata">

**Author:** ![WimM](https://avatars.discourse-cdn.com/v4/letter/w/9fc348/32.png) [@WimM](https://discuss.elastic.co/u/WimM)\
**Post date:** [November 30, 2021, 10:06am UTC](https://discuss.elastic.co/t/field-available-in-discover-is-not-available-in-visualizations/287987/7 "2021-11-30T10:06:56Z")

</div>

Thank you Graham, we will look into the explicit mapping

---

<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 28, 2021, 10:07am UTC](https://discuss.elastic.co/t/field-available-in-discover-is-not-available-in-visualizations/287987/8 "2021-12-28T10:07:13Z")

</div>

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