simitt

Required follow up tasks to make this fully work are created and assigned: - [x] https://github.com/elastic/apm-server/issues/13597 - [x] [keys not properly mapped](https://elastic.slack.com/archives/C061VM6HL8P/p1720636897196249?thread_ts=1720565616.749419&cid=C061VM6HL8P)

Holding off a bit with this, as there are currently conversations ongoing how to make the package installation a default.

As discussed today with @felixbarny , this needs more discussion and design, and therefore removed from `8.10` milestone.

Supporting tags sounds reasonable. When thinking about using APM Server managed by Fleet, users would create one Elastic Agent policy with APM and then enroll multiple Elastic Agents into this...

This could also improve CPU usage on the server side, as former investigations indicated that parsing and processing a large number of stacktrace frames is very CPU heavy.

I don't have an answer on that yet, as I saw it on stress tests and not on benchmark tests listing individual code parts. But I also don't think that...

@StephanErb it would be great if you could provide the information on whether you have sampling enabled, and if so, whether it is tail based or head based sampling. A...

@elastic/obs-ds-intake-services please give this PR a review. @carsonip has https://github.com/elastic/apm-server/issues/11671 assigned for this iteration to deprecate Jaeger, this should align with this PR.

@kruskall and I discussed yesterday to manually update the ES index template accordingly for continuing to test any performance and UI implications. Also to further look into relevant metric dimensions.

@kruskall could you investigate and add a summary related to >We should investigate whether we can switch over to TSDS without affecting the UI, or if additional changes are required....