Andrew Wilkins

@damianpfister as far as I know, investigation is ongoing (https://github.com/elastic/beats/pull/41087#issuecomment-2399999992). @gizas is that right?

> The other option is we aren't actually building with Go 1.25.4 even though it looks like we should be. The `auditbeat\build\TEST-go-unit.out.json` artifact in Buildkite claims it's using 1.25.4.

APM Server is responsible for translating data that it receives from agents into a format that is compatible with Elasticsearch, and generally speaking mapping exceptions should not be caused by...

I'd say yes, but since the collector's internal telemetry config is based on the SDK declarative configuration schema, perhaps we should document it over there? https://opentelemetry.io/docs/languages/sdk-configuration/declarative-configuration/

Is this a more general case of lazy rollover only being triggered post ingest pipeline, and not specific to rerouting? We're also seeing issues related to upgrading from older versions...

@gmarouli thanks, sounds reasonable. Just to clarify, we don't do version checks in recent versions of our ingest pipeline - that only applies to versions before 8.13.0. > If the...

@gmarouli sorry, that was very unclear, let me try again. If the data stream is marked for lazy rollover, do what you described where we resolve any settings (e.g. ingest...