Missing APM mappings


Elastic 7.9.2.

Several fields in the apm indices do not seem to have any mapping. For example (subset):

Imho, it would be nice if these fields would get a decent mapping, so we can use them to build visualisations etc. Is this on Elastic's to do or are we supposed to provide this ourselves?



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 in the apm-server.yml.
You can also find more details about this in a previous discuss post.

1 Like

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