Robert Pająk

For Go we plan to have an `slog.Handler` as log bridge. I just created an issue for tracking: https://github.com/open-telemetry/opentelemetry-go-contrib/issues/5138

Another note on > One such item was creating at least one logging bridge per SDK Log bridge DOES NOT have to be part of SDK (and I think it...

[This](https://github.com/open-telemetry/opentelemetry-specification/blob/e8d5e1416a6a491f0fc26df60a5a2bd41535a8ca/specification/logs/data-model.md#type-mapstring-any) would could to be changed to something like: > #### Type `[]keyval` > > Value of type `[]keyval` is a collection of key-value pairs with string keys to `any`...

PTAL @open-telemetry/specs-logs-approvers

Note: This is also about log record body representation (not only log attributes).

> We did find [language in the proto](https://github.com/open-telemetry/opentelemetry-proto/blob/9d139c87b52669a3e2825b835dd828b57a455a55/opentelemetry/proto/common/v1/common.proto#L57-L58) that states that keys in the `KeyValueList` type MUST be unique. Not sure how we could change that "MUST" without it being...

@jsuereth The point is that doing anything like > If Logging needs multiple values per-key, the OTLP they should use is a single key with value of List. If they...

> I understand, but someone has to pay that cost at some point. Right now this would be a large breaking change for OTLP, in my opinion unacceptably large. If...

> just be able to handle deduplication during ingest. This is good to me. PS. I did my best to update https://github.com/open-telemetry/opentelemetry-proto/pull/533 to reflect it. Also see: https://github.com/open-telemetry/opentelemetry-proto/pull/533#issuecomment-1992343984 EDIT: >...

[.NET](https://github.com/open-telemetry/opentelemetry-dotnet/blob/4cccb09239aff1250967c543f7483aaf88e538a3/src/OpenTelemetry/Logs/LogRecord.cs#L21) represents logs attributes as key-value pairs. Related issue: https://github.com/open-telemetry/opentelemetry-dotnet/issues/4324