# No cached mapping for this field --\> APM **URL:** \ **Category:** APM\ **Created:** [October 5, 2018, 10:49am UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-apm/151196 "2018-10-05T10:49:45Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![umapati](https://avatars.discourse-cdn.com/v4/letter/u/9d8465/32.png) [@umapati](https://discuss.elastic.co/u/umapati)\ **Post date:** [October 5, 2018, 10:49am UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-apm/151196/1 "2018-10-05T10:49:45Z")
I am using APM to monitor my node.js application. In Kibana, I see some fields with the error : " no cached mapping for this field". As a result, I cannot run any analytics or visualization on these fields. example of fields that are being indexed: context.request.http\_version context.request.method context.request.url.full context.request.url.hash example of fields that are not being indexed: context.request.body.app\_id context.request.body.Msg.MsgHdr.StatusCode context.request.body.Msg.MsgHdr.StatusDesc I have tried editing the fields.yml for apm-server. but i cant see those fields in the index management tab. What am I missing? ---
**Author:** ![roncohen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roncohen/32/22881_2.png) [@roncohen](https://discuss.elastic.co/u/roncohen)\ **Post date:** [October 7, 2018, 10:58pm UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-apm/151196/2 "2018-10-07T22:58:00Z")
Hi Umapati, Have you created an index pattern that matches your APM indexes? If yes, could you try to go to Settings \> Indices in Kibana and click the "Refresh field list" (yellow button) for that index pattern. Let me know if that helps. best, Ron ---
**Author:** ![umapati](https://avatars.discourse-cdn.com/v4/letter/u/9d8465/32.png) [@umapati](https://discuss.elastic.co/u/umapati)\ **Post date:** [October 8, 2018, 3:05am UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-apm/151196/3 "2018-10-08T03:05:54Z")
Hi Ron, I have update the fields.yml located @ /etc/apm-server with the missing parameters. However, I dont see them updated under kibana. ---
**Author:** ![roncohen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/roncohen/32/22881_2.png) [@roncohen](https://discuss.elastic.co/u/roncohen)\ **Post date:** [October 12, 2018, 6:24pm UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-apm/151196/4 "2018-10-12T18:24:24Z")
> [@umapati](#): > > I have update the fields.yml located @ /etc/apm-server with the missing parameters. However, I dont see them updated under kibana. Thanks! The recommended way to get additional fields indexed at the moment is to add them to "tags": [Agent API | APM Node.js Agent Reference [4.x] | Elastic](https://www.elastic.co/guide/en/apm/agent/nodejs/current/agent-api.html#apm-set-tag) For some fields that might be impossible or very inconvenient. It turns out that unfortunately 6.4 introduced a small bug which requires that you set `setup.template.fields` to `fields.yml` in order for apm-server to load the file. I've filed an issue [fields.yml is ignored but still shipped with packages · Issue #8607 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/8607). Please also make sure you've set `setup.template.overwrite: true` and that it only works for newly created indices. Let me know if that helps. /Ron ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 2, 2018, 2:24pm UTC](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-apm/151196/5 "2018-11-02T14:24:26Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.