simitt

Created a dedicated tracking issue for removing the technical blockers https://github.com/elastic/apm-server/issues/9186. This issue should be kept open until the whole feature is implemented and tested.

Moving this to backlog for now, given the scheduled issues to make the numer of `MaxRequests` configurable (https://github.com/elastic/apm-server/issues/7719) and measure the impact of a larger number (https://github.com/elastic/apm-server/issues/7718).

Good call, the auto-scaling of available bulk indexers was replaced by https://github.com/elastic/apm-server/issues/9181.

Adding `request.id` sounds reasonable! Thanks for opening the issue.

Moved it into the `8.7` milestone again to be picked up and verified if this is still a bug in current versions.

~There's a request from the Elastic Agent team to report the Fully Qualified Domain Name (FQDN) if a certain flag is set to true by the Elastic Agent.~ ~We need...

@AlexanderWert @estolfo if we want to follow the recommended value to set the lowercased FQDN for `host.name` then apm agents would need to collect this information. We could then either...

Productionized in https://github.com/elastic/apm-server/pull/9720/

Looking into this a bit, we would need to - [allow custom routing](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-put-template.html#put-index-template-api-request-body) in the index template via `datastream.allow_custom_routing: true`. This requires an update to the [package spec](https://github.com/elastic/package-spec/blob/60560379ad6ed5ffa6fc3beb13ec22ad89bdddc4/spec/integration/data_stream/manifest.spec.yml#L108-L128) to allow...

Ignoring the technicalities and details on the apm-server and index mapping for a bit - if we purely relied on the `labels` fields with `ignore_above: 1024`, then this would mean...