Robert Pająk
Robert Pająk
I have a feeling that this should be required. _Originally posted by @pellared in https://github.com/open-telemetry/opentelemetry-specification/pull/4259#discussion_r1801514796_ Setting the severity is crucial to support the most common way of filtering - by...
Context: https://github.com/open-telemetry/opentelemetry-specification/pull/4203#issuecomment-2341410062 Blocked by: - https://github.com/open-telemetry/opentelemetry-specification/pull/4203
**What are you trying to achieve?** I would like a convention on how the log bridges should report: - logger name - log bridge [package] name - log bridge [package]...
**What are you trying to achieve?** According to the docs there are only limits for the log attributes. See: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/sdk.md#logrecord-limits > LogRecord attributes MUST adhere to the [common rules of...
I think this needs updates to some of the compatibility docs (at least [prometheus](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/compatibility/prometheus_and_openmetrics.md#instrumentation-scope)). Currently, Prometheus adds scope name and scope version as labels to ensure we don't end up...
> At least some SIGs did not understand that, see the golang example We can always add functions converting standard attributes to log attributes. _Originally posted by @pellared in https://github.com/open-telemetry/opentelemetry-specification/issues/4201#issuecomment-2332304811_...
This is a portion added by @jack-berg in https://github.com/open-telemetry/opentelemetry-specification/pull/2969. I would rather not add it may lead to implementing processors which may lead to race conditions. I could change it...
Per https://github.com/open-telemetry/opentelemetry-go-build-tools/pull/921#issuecomment-2914384225 It would be also nicer for us in Go Contrib.