Robert Pająk

I have no idea. Probably you would have to debug it. [Here](https://github.com/open-telemetry/opentelemetry-go-build-tools/tree/main/semconvgen) is the source code of `semconvgen` (written in Go). [Here](https://github.com/open-telemetry/build-tools/tree/main/semantic-conventions) is the source code of `otel/semconvgen` (written in...

CC @MrAlias

On branch: ``` $ go version go version go1.21.4 linux/amd64 $ go test -run=^$ -bench=NewSetWithSortableFiltered goos: linux goarch: amd64 pkg: go.opentelemetry.io/otel/attribute cpu: Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz BenchmarkNewSetWithSortableFiltered-16 5002983...

> Hi @dmathieu , I can't see your reply in github but I do seen it in email. It was my message and I removed it after like 1 minute...

From what you wrote it is rather something with the Collector and not the SDK. As far as I remember it is possible to get logs how many spans are...

How about trying to diagnose it e.g. with Wireshark to double-check the communication between the application (OTLP exporter) and the OTel Collector?

@open-telemetry/go-instrumentation-approvers The `docs/design/log-api.md` is ready for initial review.

> It may also be good to document the package structure. For bridge API it would only be - `go.opentelemetry.io/otel/log` - `go.opentelemetry.io/otel/log/embedded` - `go.opentelemetry.io/otel/log/noop` Do you agree?

I added draft code. I left TODO comments, basically misses docs and unit tests for `Record` and `NewLoggerConfig`.

SIG meeting: @dashpole made a proposal for making record attributes as fields. We can explore if the user can use `sync.Pool` for decreasing the number of allocations. EDIT: I think...