Robert Pająk
Robert Pająk
Reuse https://github.com/open-telemetry/opentelemetry-go/pull/6342 Original assertion failures when I break 2 places: ``` --- FAIL: TestCore (0.00s) --- FAIL: TestCore/WithMultiple (0.00s) core_test.go:126: Error Trace: /home/ropajak/repos/opentelemetry-go-contrib/bridges/otelzap/core_test.go:126 Error: Not equal: expected: 3 actual :...
I propose to move [this](https://github.com/open-telemetry/opentelemetry-go-contrib/blob/main/instrumentation/README.md#new-instrumentation) section to `CONTRIUTING.md` and phrase it in a way that it applies to all new Go modules (and not just instrumentations).
Should we not take advantage of https://pkg.go.dev/go.opentelemetry.io/contrib/propagators/autoprop? Similarly for exporters we could use https://pkg.go.dev/go.opentelemetry.io/contrib/exporters/autoexport. I think that the config is supposed to be extensible and allow custom exporters, processors, propagators....
I can look and try refactoring it later. _Originally posted by @pellared in https://github.com/open-telemetry/opentelemetry-go-contrib/pull/6527#discussion_r1922411829_
Currently there are two `config` packages: - go.opentelemetry.io/contrib/config/v0.2.0 - go.opentelemetry.io/contrib/config/v0.3.0 The user should be able to have functions like `LoadYAML` in `go.opentelemetry.io/contrib/config` which gives the possibility to setup the OTel...
From the docs https://google.github.io/oss-fuzz/getting-started/new-project-guide/#status-badge: ``` Adding it is super easy, just follow this template: [](https://bugs.chromium.org/p/oss-fuzz/issues/list?sort=-opened&can=1&q=proj:) ``` However, here we have a hyperlink for `opentelemetry` project which clearly does not...
I believe it would be beneficial to release `go-cmp` as `v1`. Reasons: 1. The library is widely used, and I assume there’s no intention to introduce breaking changes while still...
Follows: - https://github.com/open-telemetry/opentelemetry-specification/pull/4535 ## Why Related to https://github.com/open-telemetry/opentelemetry-specification/issues/4540 Supersedes https://github.com/open-telemetry/opentelemetry-specification/pull/4541 per https://github.com/open-telemetry/opentelemetry-specification/pull/4541#discussion_r2138670874 and discussions from the last OTel Specification and Logs SIG meetings. **Some comments that were already expressed as...
**What are you trying to achieve?** Stabilize the following functionality: https://github.com/open-telemetry/opentelemetry-specification/blob/d2035751f3fc89a1ef44eb883dac63facc913138/specification/logs/api.md?plain=1#L127-L133
**What are you trying to achieve?** It may be good to allow having EventId of an integer type (instead of EventName which is always as string) for performance reasons. **Additional...