Robert Pająk
Robert Pająk
Towards https://github.com/open-telemetry/opentelemetry-go/issues/5219 Related to https://github.com/open-telemetry/opentelemetry-specification/issues/4065 Alternative proposal: https://github.com/open-telemetry/opentelemetry-go/pull/5469 Changes `Processor.OnEmit` to: ```go OnEmit(ctx context.Context, record Record) (Record, error) ``` Pros: - MAY be seen as acceptable by spec (however, probably...
Fixes https://github.com/open-telemetry/opentelemetry-go/issues/5219 Related to https://github.com/open-telemetry/opentelemetry-specification/issues/4065 Alternative proposal: https://github.com/open-telemetry/opentelemetry-go/pull/5470 Changes `Processor.OnEmit` to: ```go OnEmit(ctx context.Context, record *Record) error ``` Pros: - compliant with the specification - design similar to span processors...
**Is your feature request related to a problem? Please describe.** There is no information how to verify to collector's **binary** signature. The releases contain a lot of artifacts related to...
Per https://github.com/open-telemetry/opentelemetry-specification/pull/4062 > #### Isolating processor > > **Status**: [Development](../document-status.md) > > This is an implementation of `LogRecordProcessor` ensuring the log record > passed to `OnEmit` of the configured `processor`...
It looks like `instrgen` is no longer maintained. https://github.com/open-telemetry/opentelemetry-go-contrib/pull/3682 is the last PR which was submitted more than year a ago. I propose removing `instrgen` unless there is someone willing...
Add [`zapcore.Core`](https://pkg.go.dev/go.uber.org/zap/zapcore#Core) log bridge.
A lot of logging libraries simply accept an `io.Writer` for configuration. E.g. - https://pkg.go.dev/log#SetOutput - https://pkg.go.dev/k8s.io/klog#SetOutput We could provide a generic log bridge which returns an `io.Writer`. That would allow...
Add [logr.LogSink](https://pkg.go.dev/github.com/go-logr/logr#LogSink) log bridge. Prototype implementation: https://github.com/pellared/opentelemetry-go/blob/147762ffb5c4394417b3f973274cc570723db79b/log/internal/logr.go TODO: - [ ] Implementation: (draft: https://github.com/open-telemetry/opentelemetry-go-contrib/pull/5357) - [ ] Benchmarks - [ ] Add to published modules - [ ] Add to...
Fixes https://github.com/open-telemetry/opentelemetry-specification/issues/4065 Per https://github.com/open-telemetry/opentelemetry-specification/issues/4065#issuecomment-2147846667 Allow chaining processors and having the log record modifications local. This is how currently [C++](https://github.com/open-telemetry/opentelemetry-specification/issues/4010#issuecomment-2096577303) (stable), Go (beta) Logs SDK are designed. For reference, the following...
Follows https://github.com/open-telemetry/opentelemetry-specification/pull/4062 ## Why 1. There is a need to make a deep copy of a `ReadWriteRecord` in order to implement an experimental isolating processor outside of the SDK (as...