Robert Pająk
Robert Pająk
From https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#span-limits: > There SHOULD be a message printed in the SDK's log to indicate to the user that an attribute was discarded due to such a limit. To prevent...
- Add package level documentation - Add testable examples
**Blocked by:** - https://github.com/open-telemetry/opentelemetry-go/issues/5086 ## What Add `WithoutDedup` option to turn off deduplication (allow duplicated key-values) in simple and batch log record processors. ## Why 1. There is a similar...
Per https://github.com/open-telemetry/opentelemetry-specification/pull/3801 The new wording makes Go implementation non-compliant, but it's not a breaking change for its API, you will just need to relax the checks (i.e. never return errors...
### Problem Statement From https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/bridge-api.md#loggerprovider > Normally, the `LoggerProvider` is expected to be accessed from a central place. Thus, the API SHOULD provide a way to set/register and access a...
I guess to avoid developer confusion as we develop this it would be best to remove this and track its addition with an issue on the GA project. _Originally posted...
Towards https://github.com/open-telemetry/opentelemetry-go/issues/5065
Towards https://github.com/open-telemetry/opentelemetry-go/issues/5065 Follow our own docs. From `Processor.Enabled` docs: > Before modifying a Record, the implementation must use Record.Clone to create a copy that shares no state with the original.
_Only sdk/log module is changed._ Per https://github.com/open-telemetry/opentelemetry-go/pull/5469#issuecomment-2145588742 Pros: - compliant with the specification - the most similar design to span processors Cons: - The worst performance (see benchmark results below),...