Andrew Wilkins

@smalenfant can you please include your full collector config?

@smalenfant thanks! I wonder if that should be the default. The README says: > If a file is updated or added, the receiver will read it in its entirety again....

I don't love https://github.com/elastic/elasticsearch/pull/112097 as a solution, since it kinda implies we'll keep the old ILM config around in the index templates for perpetuity. Perhaps we can remove that while...

We need to handle the following scenarios: - Create a new 8.15.1+ cluster, with defaults: DLM should be used - Create a new 8.15.1+ cluster, with customised ILM (https://www.elastic.co/guide/en/observability/current/apm-ilm-how-to.html#apm-data-streams-custom-three): customised...

> This, as expected, creates unmanaged indices. We would need to suggest workaround for this in our changelog/release-notes. The simplest way would be to have users with default ILM settings...

I think it makes sense to support SO_REUSEPORT/SO_REUSEADDR. Do you see any downsides to always enabling this, rather than making it configurable? Previous issues that went stale: - https://github.com/open-telemetry/opentelemetry-collector/issues/2607 -...

Fair call. If you're interested in implementing this, please let me know and I can assign it to you.

@mx-psi suggested in https://github.com/open-telemetry/opentelemetry-collector/pull/13950#discussion_r2428385177: > I think we can even hint the user to use otelconftelemetry.NewFactory, since users seeing this error message most likely would want to use that factory.

It's possible to opt out of resource attributes through configuration by setting them to `null` under `service::telemetry::resource`. e.g. ```yaml service: telemetry: resource: service.instance.id: null service.name: null service.version: null ``` ......

I started looking at documenting it, but figured I may as well make the code change to disable it by default at the same time: https://github.com/open-telemetry/opentelemetry-collector/pull/14094