Edoardo Tenani

I've been working on this for the 8.17.5 release. Unfortunately the `8.17.5` automation was already run ~2 weeks ago https://github.com/elastic/apm-server/pull/16416, so I've only been able to partially test this, as...

The current situation is more convoluted than expected. TL;DR: the current automation is not working. This will impact the next minor releases. ## Next minors Next minors in `main` (9.x)...

9.x release automation is now working as expected. I'll proceed testing that 8.x still works as expected.

I confirmed 8.x automation works: the automation did not work already for changelogs on patch releases, requiring manual action, so we are covered there. As minors in 8.x are expected...

The PR with 9.x automation is up and waiting for team review: https://github.com/elastic/apm-server/pull/16358

I created the PR to update the documentation and close this issue, it's now ready for review.

Upon a first review I think we are covered. The data stream we use in 9.x: * `traces-apm` * `traces-apm.rum-` * `metrics-apm.internal-` * `metrics-apm.transaction.-` * `metrics-apm.service_destination.-` - `metrics-apm.service_transaction.-` - `metrics-apm.service_summary.-`...

Testing was postponed due to other work items.

I've investigated this a bit more. Before delving into the logic of this, I think there is a workaround: [configure](https://www.elastic.co/guide/en/beats/metricbeat/current/configuration-general-options.html#_tags_2) `tags` in Metricbeat configuration file to desired values. The trade...

Updates on my investigation. TLDR: this is not possible to fix in its entirety but there are a couple of workarounds worth exploring that would help mitigating the problem. #...