# Missing APM mappings

**URL:** <https://discuss.elastic.co/t/missing-apm-mappings/256482>\
**Category:** APM\
**Tags:** server\
**Created:** [November 24, 2020, 10:05am UTC](https://discuss.elastic.co/t/missing-apm-mappings/256482 "2020-11-24T10:05:37Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [November 24, 2020, 10:27am UTC](https://discuss.elastic.co/t/missing-apm-mappings/256482/2 "2020-11-24T10:27:34Z")

</div>

Hi @willemdh,

not indexing the HTTP request and response headers by default was a conscious decision to avoid indexing a potentially large number of fields that don't need to be queried by the APM UI.

It is possible though to enable dynamic mappings for these fields, by setting [`setup.template.append_fields`](https://www.elastic.co/guide/en/apm/server/current/configuration-template.html) in the `apm-server.yml`.  
You can also find more details about this in a [previous discuss post](https://discuss.elastic.co/t/apm-index-not-refreshing-in-kibana-getting-mapper-exception/243063/5).

---

_[View the full topic](https://discuss.elastic.co/t/missing-apm-mappings/256482)._