Robert Pająk

@open-telemetry/technical-committee, can I propose a PR based on Proposal A and Go implementation?

@tigrannajaryan, I am not working on PR as the label is `triage:deciding` and not `triage:accepted`. This the reason I asked > @open-telemetry/technical-committee, can I propose a PR based on Proposal...

I am not sure what "clean'" design means here but I think that the config design misses the fundamental functionality of supporting different log record processing pipelines. E.g. https://github.com/open-telemetry/opentelemetry-specification/issues/4207#issuecomment-2377517345 or...

> Presumably there's parts of those systems which encourage the pattern of calling user code in a similar scenario as our Logger#enabled operation? Not sure whether calling "encourage" is a...

We had chat with @tigrannajaryan. Here is a summary: 1. We need to define use-cases that would help decision making and driving the design. E.g. log filtering coupled to trace...

Summary from https://cloud-native.slack.com/archives/C062HUREGUV/p1731580335908619: I start to lean towards exploring **Proposal C - Extend Logger config** with `min_severity_level` (https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/sdk.md#loggerconfig). I does not require adding any new concept the SDK and should...

SIG meeting notes: Go pkg docs: - https://pkg.go.dev/go.opentelemetry.io/otel/log/logtest - https://pkg.go.dev/go.opentelemetry.io/otel/sdk/log/logtest Having releases will also make it easier to see breaking changes between versions.

PTAL @open-telemetry/specs-logs-approvers

@jack-berg, I do not think that it would be good to use `AttributeValueLengthLimit` and `AttributeCountLimit` for `Body`. Reasons: 1. "we probably don't need to apply the same strict limits, though...

Hard for me to evaluate as Logs are still Beta in OTel Go and personally, I have no feedback on how much this feature is needed. I think we can...