So the documentation there is not accurate, the APM Server does check for the URL path leaving out the scheme and host, so it should match anyways.
I will make a note to update the docs, but I can't reproduce the issue. Does it keep happening?
What APM Server version are you using?
Is it possible that you deployed a new version of your app, but didn't update the sourcemap, or something like that?
Oh ok great! In that case, I'm not sure what's going wrong then...
We're using the latest APM version (7.7). We added the source map upload as part of our build process using this package https://www.npmjs.com/package/elastic-apm-sourcemap-webpack-plugin, and from the logs it seems like there should be a source map available for the current version of our app.
This is the error we're seeing in our actual logs - any ideas how else to debug this?
Ok, so we can start checking if there is an actual sourcemap indexed (I assume there is, but is a good place to start).
A query to Elasticsearch like this one would help:
I think I had the apm server endpoint url wrong That query worked though! And once I updated the url, was able to confirm via that query the source maps were uploaded, and now I'm seeing the mapped logs in Kibana!
Thanks for helping me debug, this is super helpful
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.