# Issue with refreshing fields in kibana

**URL:** <https://discuss.elastic.co/t/issue-with-refreshing-fields-in-kibana/145104>\
**Category:** Kibana\
**Created:** [August 20, 2018, 7:25am UTC](https://discuss.elastic.co/t/issue-with-refreshing-fields-in-kibana/145104 "2018-08-20T07:25:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![vissu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vissu/32/33833_2.png) [@vissu](https://discuss.elastic.co/u/vissu)\
**Post date:** [August 20, 2018, 7:25am UTC](https://discuss.elastic.co/t/issue-with-refreshing-fields-in-kibana/145104/1 "2018-08-20T07:25:17Z")

</div>

Hi Team,

We are using ELK v 6.3.1. We are facing one issue while viewing cluster **monitoring data** in kibana.  
For few fields i see a caution symbol which says " **No Cached mapping for this filed. Refresh field list from the management \> index patterns page**" for example for the field **indices\_stats.\_all.total.store.size\_in\_bytes**. Even after refreshing as decribed above, this caution symbol is still there and no fields are added.

what is the solution for this ?

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [August 20, 2018, 6:21pm UTC](https://discuss.elastic.co/t/issue-with-refreshing-fields-in-kibana/145104/2 "2018-08-20T18:21:20Z")

</div>

> [@vissu](#):
>
> No Cached mapping for this filed.

This is done purposefully for now. We cache the mapping because large mappings are expensive to parse. We cache the normalized mapping to keep things speedy. We're looking into methods of offering a warning. Reloading field data manually through settings solves this.

Am also tagging @pickypg / @tsullivan here for more detailed response from the monitoring perspective.

Thanks  
Rashmi

---

<div class="post-metadata">

**Author:** ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)\
**Post date:** [August 20, 2018, 7:37pm UTC](https://discuss.elastic.co/t/issue-with-refreshing-fields-in-kibana/145104/4 "2018-08-20T19:37:59Z")

</div>

@vissu

That field is not something we currently have in the mappings or something we show in the UI. If you'd like to use that field for your own purposes (which it sounds like is the case), I'd recommend creating [an index template](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-templates.html) to match the `.monitoring-es-6*` index pattern, then define your own mappings to account for any fields you want to use.

You can view the existing index template used internally by running this command in the dev console: `GET _template/.monitoring-es`.

Let me know if this helps!

---

<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:** [September 17, 2018, 7:38pm UTC](https://discuss.elastic.co/t/issue-with-refreshing-fields-in-kibana/145104/5 "2018-09-17T19:38:00Z")

</div>

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