Can't get container.id from auto instrumentation about opentelemetry-go-instrumentation HOT 5 OPEN

we would like to keep it as much automated as possible

Why would usage of https://github.com/open-telemetry/opentelemetry-operator be not (or less) automated?

from opentelemetry-go-instrumentation.

Is using an OTel Collector on the same pod an acceptable solution? You may also be interested in https://github.com/open-telemetry/opentelemetry-operator.

from opentelemetry-go-instrumentation.

@pellared in my scenario is not a suitable solution, I'm leveraging an automated mechanism in my platform where the collector is running on a separate pod, we would like to keep it as much automated as possible

from opentelemetry-go-instrumentation.

I was wondering if there is some tiny mistake on the script definition in OTEL_RESOURCE_ATTRIBUTES that prevents the container.id to be reached and gives me the script itself instead

from opentelemetry-go-instrumentation.

Would it be possible to add some of the existing resource detectors into the auto instrumentation, e.g. some of this code:

https://github.com/open-telemetry/opentelemetry.io/blob/05a7dfa420911704c8a234a1783555e431b5ef50/content/en/docs/languages/go/resources.md?plain=1#L39

being added here:

from opentelemetry-go-instrumentation.