APM server producing errors (mapper_parsing_exception) when traces are sent through jaeger-agent

[axw (Andrew Wilkins)]

Welcome to the forum @Amirtheahmed!

Do you have multiple services instrumented? That sort of error would occur when the instrumentation provides two different data types for the same attribute.

If this is the case, then I think the simplest short-term solution would be to split services into multiple indices, to avoid these kinds of mapping conflicts:

Storing APM data in custom/specific indices

If you'd like to split your APM indices by the service, you can use the advice from this topic. You can change the index name by setting either output.elasticsearch.index or output.elasticsearch.indices. These configuration variables take an index name "format string", which can reference fields the events. For your use-case, you can include %{[service.name]} in the format string to create an index per service. e.g. output.elasticsearch: hosts: ["http://localhost:9200"] indices: - inde…