You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From 8.7 onwards, the APM Server (standalone & managed by Elastic Agent) fetches sourcemaps directly from Elasticsearch. For backwards compatibility we still support fetching from Kibana, but only as a fallback.
What changed?
APM Kibana changed the internal logic to always write sourcemaps to a newly introduced system index in Elasticsearch, from which the APM Server can read them. Sourcemaps are no longer passed to the APM Server via Fleet configuration.
Available config options: apm-server.rum.source_mapping.elasticsearch.* if no dedicated elasticsearch config is set, the standard output elasticsearch configuration is used .
Fleet managed: automatically filled
Elastic Agent standalone or APM Server standalone : user configurable
From
8.7
onwards, the APM Server (standalone & managed by Elastic Agent) fetches sourcemaps directly from Elasticsearch. For backwards compatibility we still support fetching from Kibana, but only as a fallback.What changed?
APM Kibana changed the internal logic to always write sourcemaps to a newly introduced system index in Elasticsearch, from which the APM Server can read them. Sourcemaps are no longer passed to the APM Server via Fleet configuration.
Available config options:
apm-server.rum.source_mapping.elasticsearch.*
if no dedicated elasticsearch config is set, the standard output elasticsearch configuration is used .More details in #9643
The text was updated successfully, but these errors were encountered: