Gerhard Stöbich

Do you think about removing the "burden" to manually install OTel components like SDK, exporter,... by selecting a specific set of them and include it into node core? I fear...

Shipping preconfigured/zero config packages for OTel is usually done by APM tool vendors. They know/decide on details like * export protocol * export endpoints * authentication on these endpoints *...

> My understanding from [proposing auto-instrumentation for `node:sqlite`](https://github.com/open-telemetry/opentelemetry-js-contrib/issues/2698) is that the OTel team isn't overly eager to support this (but maybe I'm wrong there). A concrete instrumentation for `node:sqlite` is...

I don't think we should rely on a single user to decide on propagating hooks to workers or not. Loader hooks are often just an implementation detail of some tool....

if someone sets an env var to use `foo` exporter which is not installed it will fail. If someone would like to switch without changes in package.json between x exporters...

I think (3) results in the easiest to understand and maintainable solution for node core and hooks maintainers. I see not that much of a gain we got from moving...

The API 1.1.0 is fine as is. But a version of [sdk-trace-base](https://github.com/open-telemetry/opentelemetry-js/tree/main/packages/opentelemetry-sdk-trace-base) supporting it is not yet released (it's an ongoing task). So if you are only interested in the...

as said above it depends what you want. If you would like to combine various otel packages you have to take care to use versions which work together. If you...

As a `SpanProcessor` gets the real span in `onStart` it's not really a protection. I could imagine that there are `SpanProcessor` implementations which add some property to the span received...

So this means the object passed to `onStart` is never passed to `onEnd`?