ET

I understand how they are different (application internal vs. external collector), but in practice there does appear to be significant overlap between this and the [k8sattributes processor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/k8sattributesprocessor) in the OpenTelemetry...

Test failure seems to be unrelated to these changes.

I'm interested in this same functionality but for use as an AutoConfigureSpi addition to a manually instrumented program (which uses the AutoConfigure SDK extension). Is there anything which ties `AgentTracerProviderConfigurer`...

Until this is supported by nodejs itself (7.2?), we are not going to add such a feature to this module. Instead, the assumption is that those using this module understand...

I want to reopen this as this is still something we'd like to be able to obtain from the k8sattributes processor in the OpenTelemetry Collector. What we want to do...

@ChrsMark After thinking about this more (and also writing an implementation), I think I'm going to close this PR and start a new one, leaving this one here for reference....

Yes, ideally there would be some sort of global setting for OpenTelemetry Resource, and the trace/metrics/logging OpenTelemetry exporters would refer to that when initializing themselves, so that the resource information...

@joaopgrassi I think this is still important. Is it possible to label this as `help wanted`?