Robert Pająk

Related issue: - https://github.com/open-telemetry/opentelemetry-specification/issues/2232

@jba Do you want to participate (in any way you feel comfortable with) in adding logs to OpenTelemetry Go? I would be more than happy to get any feedback from...

Closing per https://github.com/open-telemetry/opentelemetry-go/pull/4809. New issues will be created e.g. for SDK design.

Please [create a minimal, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example). You can even create a dedicated repository if it would be easier for you. Also please provide more information e.g. how you create a...

@pdeva Do you plan to add more information that is needed to work on this issue? We need complete (compiling) code and steps that reproduces the issue.

1. Is there OTLP exporter in any other language who works that way? 2. This behavior is not specified in https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/exporter.md. > have an option to be reloaded, when they...

See https://github.com/go-logr/logr/blob/master/slogr/example/main.go to check how to plug a slog handler as logr logger. More: https://pkg.go.dev/github.com/go-logr/logr

Correct, we decided to use `logr` as the logging abstraction instead of creating our own. `logr` was created for this purpose. `slog` was not available when we were building OTel...

> Maybe if the Go std lib developers had introduced the slog earlier (or they had integrated logr), we wouldn't be in this situation now. This is correct. We added...

> I have an issue with using logr. Using `go-logr/zapr` to wrap our Uber Zap logger, it prints / gives incorrect log levels. This is because otel uses 0, 1,...