Tyler Yahn

> In our implementation, we define all the initialization logic for the instrumentation within the `init()` method, ensuring that the main file of the application being instrumented imports this module...

> @MrAlias Thank you for your suggestion. It is indeed a feasible option. However, this means that spans created by users with the `go-sdk` would be completely separate from those...

Blocked by https://github.com/open-telemetry/semantic-conventions/issues/1031 or a workaround.

Superseded by https://github.com/open-telemetry/opentelemetry-go/pull/5476

The [`versions.yaml`](https://github.com/open-telemetry/opentelemetry-go/blob/30cc3794666b1cdd2c8e2cb6580b9d72b5731f79/versions.yaml#L49) entry and changelog still need to be updated to complete the release.

> I want to work on this! Should I update `ScopeLogs` as well? > > https://github.com/open-telemetry/opentelemetry-go/blob/fe3de7059e19a0e88c7e8b342ed345e50df94aa3/exporters/otlp/otlplog/otlploghttp/internal/transform/log.go#L56 I would start by only pooling the maps.

This needs to be applied at to the template to address both HTTP and gRPC: https://github.com/open-telemetry/opentelemetry-go/tree/main/internal/shared/otlp/otlplog/transform

Possible duplicate of https://github.com/open-telemetry/opentelemetry-go/issues/3808

Also blocked by https://github.com/open-telemetry/opentelemetry-specification/issues/2039. The logging levels we implement need to be compatible with other langauges.

> Cuurently is there any way to change log level for Golang? [Register](https://pkg.go.dev/go.opentelemetry.io/otel#SetLogger) a `logr.Logger` with the desired logging level.