When using another output than Elasticsearch (your latest apm-server.yml shows you are using Kafka) you should ensure the index templates, ingest pipelines, etc. are loaded to Elasticsearch before starting to ingest data. You can do so by running
If you do not provide any Elasticsearch configuration, sourcemaps cannot be applied. However that has no impact on displaying APM data in general in Kibana.
Please see my post above on what you need to consider when working with an output different than Elasticsearch (Kafka in your case).
I use kafka storage, how to configure sourcemap to elasticsearch?
If multiple outputs are configured in apm-server.yml, apm-server cannot start normally
What kind of marks are there in the apmserver log for apm-ui to work properly? @simitt
Configure the Elasticsearch source map retrieval location, taking the same options as output.elasticsearch. This must be set when using an output other than Elasticsearch, and that output is writing to Elasticsearch. Otherwise leave this section empty.
This means that if you use a different output than elasticsearch, you can still configure elasticsearch in apm-server.rum.source_mapping.elasticsearch.*.
So that would mean you configure something like:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.