# Ability to add more exported fields in APM

**URL:** <https://discuss.elastic.co/t/ability-to-add-more-exported-fields-in-apm/151245>\
**Category:** APM\
**Created:** [October 5, 2018, 3:58pm UTC](https://discuss.elastic.co/t/ability-to-add-more-exported-fields-in-apm/151245 "2018-10-05T15:58:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**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, 3:58pm UTC](https://discuss.elastic.co/t/ability-to-add-more-exported-fields-in-apm/151245/1 "2018-10-05T15:58:40Z")

</div>

[https://www.elastic.co/guide/en/apm/server/6.0/exported-fields-apm.html](https://www.elastic.co/guide/en/apm/server/6.0/exported-fields-apm.html)

ref to the above post, If my request/response has additional fields, how do i make sure it gets indexed?

I am using APM 6.0

---

<div class="post-metadata">

**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\
**Post date:** [October 7, 2018, 8:03am UTC](https://discuss.elastic.co/t/ability-to-add-more-exported-fields-in-apm/151245/2 "2018-10-07T08:03:30Z")

</div>

Generally, you can add additional information that should be indexed via `tags`. If you don't need to search or aggregate on the information you can add it via `custom` context.

Not sure which agent you are using, so I am linking to the [python agent docs](https://www.elastic.co/guide/en/apm/agent/python/current/api.html#api-tag) for an example.

Note that APM 6.0 was in alpha. You might want to consider upgrading to a newer version.

---

<div class="post-metadata">

**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:14am UTC](https://discuss.elastic.co/t/ability-to-add-more-exported-fields-in-apm/151245/3 "2018-10-08T03:14:25Z")

</div>

I am using node.js agent. the apm and the entire ELK stack is updated too-\>  
2018-10-08T11:10:03.569+0800 INFO instance/beat.go:225 Setup Beat: apm-server; Version: 6.3.0

the issue may be not related to the version of the apm.

maybe I am unable to articulate the problem clearly/correctly.

I am providing a screenshot from kibana to see if it can help.

![image](https://us1.discourse-cdn.com/elastic/original/3X/4/7/47e5fd1129dd73b0f3cc3280577ef8f1f615a6ab.png)

as you can see, the fields are captured but not indexed.

---

<div class="post-metadata">

**Author:** ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)\
**Post date:** [October 16, 2018, 1:08pm UTC](https://discuss.elastic.co/t/ability-to-add-more-exported-fields-in-apm/151245/4 "2018-10-16T13:08:25Z")

</div>

By default only defined attributes sent from the agents are indexed. Please refer to [No cached mapping for this field --\> APM](https://discuss.elastic.co/t/no-cached-mapping-for-this-field-apm/151196/4) for instructions on how you can add fields to be indexed.

---

<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:** [November 6, 2018, 9:08am UTC](https://discuss.elastic.co/t/ability-to-add-more-exported-fields-in-apm/151245/5 "2018-11-06T09:08:28Z")

</div>

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